Overlapping transmission in urllc

ABSTRACT

There is disclosed a method of operating a wireless device in a wireless communication network, the wireless device being triggered for transmitting first signaling representing first information on a first resource structure, second signaling representing second information on a second resource structure and third signaling representing third information on a third resource structure, the second resource structure at least partially overlapping with the first resource structure and/or the third resource structure, the second resource structure being associated to a lower priority of transmission than the first resource structure and the third resource structure, the method including transmitting the first information and the third information, omitting transmitting the second signaling and/or second information. The disclosure also pertains to related devices and methods.

TECHNICAL FIELD

This disclosure pertains to wireless communication technology, inparticular regarding use of transmission resources for uplinktransmission.

BACKGROUND

Modern wireless communication systems have powerful approaches ofmanaging resources, in particular time and/or frequency and/or coderesources. In some cases, different resources, e.g. for uplinktransmission, may overlap or be ambiguously assigned to a wirelessdevice. There are needed approaches facilitating managing large and/oroverlapping sets of resources.

SUMMARY

It is an object of the present disclosure to provide approaches allowingimproved handling of communication resources, in particular for uplinktransmission, for example in the context of prioritisation of specificsignaling like URLLC signaling, in particular on the physical layer. Theapproaches are particularly advantageously implemented in a 5^(th)Generation (5G) telecommunication network or 5G radio access technologyor network (RAT/RAN), in particular according to 3GPP (3^(rd) GenerationPartnership Project, a standardisation organization). A suitable RAN mayin particular be a RAN according to NR, for example release 15 or later,or LTE Evolution.

There is disclosed a method of operating a wireless device in a wirelesscommunication network. The wireless device is triggered for transmittingfirst signaling representing first information on a first resourcestructure, triggered for transmitting second signaling representingsecond information on a second resource structure and triggered fortransmitting third signaling representing third information on a thirdresource structure. The second resource structure is at least partiallyoverlapping with the first resource structure and/or the third resourcestructure. The second resource structure is associated to a lowerpriority of transmission than the first resource structure and the thirdresource structure. The method comprises transmitting the firstinformation and the third information, omitting transmitting the secondsignaling and/or second information.

There is also described a wireless device for a wireless communicationnetwork. The wireless device is adapted for triggered for transmittingfirst signaling representing first information on a first resourcestructure, triggered for transmitting second signaling representingsecond information on a second resource structure and triggered fortransmitting third signaling representing third information on a thirdresource structure. The second resource structure is at least partiallyoverlapping with the first resource structure and/or the third resourcestructure, and the second resource structure is associated to a lowerpriority of transmission than the first resource structure and the thirdresource structure. The wireless device is adapted for transmitting thefirst information and the third information, omitting transmitting thesecond signaling and/or second information.

Moreover, a method of operating a network node in a wirelesscommunication network is proposed. The method comprises receivingsignaling from a wireless device, the wireless device being triggeredfor transmitting first signaling representing first information on afirst resource structure, second signaling representing secondinformation on a second resource structure and third signalingrepresenting third information on a third resource structure. The secondresource structure is at least partially overlapping with the firstresource structure and/or the third resource structure, and the secondresource structure is associated to a lower priority of transmissionthan the first resource structure and the third resource structure.Receiving signaling comprises receiving signaling representing the firstinformation and the third information, omitting the second information.

There may be considered a network node for a wireless communicationnetwork. The network node is adapted for receiving signaling from awireless device, the wireless device being triggered for transmittingfirst signaling representing first information on a first resourcestructure, second signaling representing second information on a secondresource structure and third signaling representing third information ona third resource structure. The second resource structure is at leastpartially overlapping with the first resource structure and/or the thirdresource structure, and the second resource structure is associated to alower priority of transmission than the first resource structure and thethird resource structure. Receiving signaling comprises receivingsignaling representing the first information and the third information,omitting the second information.

The first resource structure, the second resource structure and thethird resource structure may be in the same transmission timingstructure. Omitting transmitting the second information or secondsignaling may be limited to this transmission timing structure, and maycomprise postponing transmission of the second information, e.g. in alater transmission timing structure. The transmission timing structuremay in particular be a slot or subslot.

In general, the first resource structure may at least partially overlapwith the third resource structure in time. However, cases in which theydo not overlap may be considered. The second resource structure may atleast partially overlap in time with either or both of the first andthird resource structures. There may be considered cases with multiplesecond signalings on different second resource structures with lowpriority being triggered.

A first priority of the first signaling is associated to a firsttransmission quality, and/or a second priority of the second signalingis associated to second transmission quality, and/or a third priority ofthe third signaling is associated to a third transmission quality. Thesecond priority may be lower than the first and/or third priority. Thefirst and third priority may be the same. The first and third prioritymay correspond to URLLC operation, and the second priority maycorrespond to eMBB operation, or to URLLC operation with lower prioritythen the priority or priorities of the first and/or third signaling.

It may be considered that the first information and third informationare multiplexed and transmitted on a common resource structure. This maybe in particular the case if the first resource structure and the thirdresource structure overlap at least partially in time, or areneighbouring in time, or if one represents data (like user data and/or aUL-SCH channel) and the other control information (e.g., UCI), in whichcase the common resource structure may be the first or third resourcestructure associated to data signaling or a data channel like PUSCH(e.g, URLLC PUSCH). Alternatively, it may be considered that the firstsignaling is transmitted on the first resource structure and the thirdsignaling is transmitted on the third resource structure, for example ifthe resource structures are apart, e.g. at least one symbol apart intime, and/or are associated to control information like first controlinformation and third control information, respectively.

It may be considered that the first signaling, second signaling andthird signaling represent control signaling, e.g. representing UCItriggered to be transmitted on three different PUCCH resources.

In general, transmission of signaling representing the secondinformation may be postponed, e.g. to a later slot or subslot. Thus, theinformation is not lost. Presumably, the lower priority is associated toa lower latency requirement, such that postponing transmission of thesecond information may not too negatively impact the operation.

In some cases, different transmission qualities may correspond todifferent service requirements and/or priorities. In particular, one ofthe transmissions and/or resource structures and/or information may beprioritised higher than the other. A transmission quality may generallyindicate and/or be represented by a latency requirement. Differenttransmissions or different transmission qualities may have differentlatency requirements. A higher latency requirement in general mayindicate a shorter time for transmission than a lower latencyrequirement. The approaches disclosed herein facilitate efficient use ofresources while following latency requirements, e.g. in the context ofURLLC. In some cases, higher priority does not coincide with higherlatency requirement, e.g. due to configuration and/or service setup byan operator and/or according to a prioritisation representation and/orif a service requiring higher reliability is prioritised. In this case,it may still be useful to fulfil the higher latency requirements, and ifmultiplexing is not possible, to omit or shift the higher prioritytransmission.

In some cases, multiplexing of the third information and firstinformation may be dependent on the common resource structure ending intime before or at the end of a predetermined time window, which may be alatency window. The end (in time domain) of the time window may be basedon a latency requirement for the first information and/or first resourcestructure and/or the third information and/or third resource structure;higher latency may correspond to an earlier end of the latency window,e.g. based on the same reference.

A duration of a predetermined time window may be dependent on atransmission type and/or priority of the information blocks and/orassociated to the resource structures. The duration may in particular bedependent on the latency requirement of the transmission or informationor resource structure with the higher latency requirement.

A wireless device may be implemented as user equipment or terminal. Thewireless device may comprise, and/or be implemented as, and/or beadapted to utilise, processing circuitry and/or radio circuitry, inparticular a transceiver and/or transmitter and/or receiver, fortransmitting signaling and/or control information and/or communicationsignaling and/or data signaling, and/or for receiving subject signalingand/or control signaling, e.g., the control information message.

A network node may be implemented as a radio network node, e.g. as gNBor IAB (Integrated Access and Backhaul) node or relay node or basestation. In some cases, it may be implemented a wireless device or userequipment, e.g. in a sidelink scenario. The network node may comprise,and/or be implemented as, and/or be adapted to utilise, processingcircuitry and/or radio circuitry, in particular a transceiver and/ortransmitter and/or receiver, for transmitting a control informationmessage and/or other control or data signaling and/or configuring and/ortriggering a wireless device, and/or for receiving (e.g., communicationor data or control) signaling. The wireless communication network may bea Radio Access Network (RAN), in particular a 5G RAN or NR RAN, or insome scenarios a sidelink or D2D (Device-to-Device) network or IABnetwork.

There is also considered a program product comprising instructionsadapted for causing processing circuitry to control and/or perform amethod as described herein. Moreover, a carrier medium arrangementcarrying and/or storing a program product as described herein may beconsidered. A system comprising a network node and a UE as describedherein is also described, as well as an associated information system.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings are provided to illustrate concepts and approachesdescribed herein, and are not intended to limit their scope. Thedrawings comprise:

FIG. 1, showing an exemplary scenario for overlapping signaling;

FIG. 2, showing an example of a radio node implemented as a terminal orUE; and

FIG. 3, showing an example of a radio node implemented as a networknode, in particular a gNB.

DETAILED DESCRIPTION

In the following, concepts and approaches are described in the contextof NR technology. However, the concepts and approaches may be applied toother RATs. Moreover, the concepts and approaches are discussed in thecontext of communication between network node (gNB) and UE, for uplinktransmission of communication signaling, but also may be applied todownlink transmission scenarios in some cases. They may be generallyapplied to a sidelink scenario, in which case both involved radio nodesmay be UEs, or in a backhaul or relay scenario, in which cases bothradio nodes may be network nodes.

FIG. 1 shows an exemplary scenario for overlapping signaling. As can beseen, in a slot (or subslot), there are available or triggeredtransmissions on a first resource structure RS10, a second resourcestructure RS14 and a third resource structure RS12. The resourcestructure RS14 is associated to transmission of PUCCH/UCI in eMBB mode,whereas resource structures RS10 and RS12 are associated to PUCCH/UCItransmission in URLLC mode. Resource structure RS14 in the exampleoverlaps with resource structures RS10 and RS12 in time (the x-axisreferring to the slot may represent time, the y-axis frequency).However, in this example, the first and third resource structures RS 10,RS 12 do not overlap with each other. As is indicated by the resourcestructure RS14 being crossed out, the triggered transmission of thesecond signaling and/or second information is omitted (or postponed,respectively). In the example, the first information and thirdinformation associated to the triggered transmissions on the firstresource structure RD10 and the third resource structure RS12 may bemultiplexed on a common resource structure RS20, which may be selectedaccording to size (to be able to carry the first information and thesecond information according to transmission quality requirements)and/or such that is within a latency window. The second information isnot multiplexed on the common resource structure RS20.

A transmission quality may indicate and/or represent and/or correspondto and/or be associated to one or more transmission parameters regardingand/or pertaining to communication quality or quality requirement/sand/or target/s, in particular regarding a transmission error rate likeBLER and/or BER and/or a latency and/or a type of transmission ortransmission mode (e.g,, URLLC or eMBB) and/or priority and/or qualityof service. A transmission quality may be associated to and/or pertainto an operation mode and/or one or more channel, in particular physicalchannel/s and/or logical channel/s or logical channel group. Several(physical and/or logical) channels may be associated a transmissionquality and/or transmission mode or operation mode, in particularcontrol channels like PUCCH and/or PDCCH and data channels like PUSCHand/or PDSCH. The control channels may pertain to the associated datachannels, e.g. for controlling communication of data via these datachannels. It may be considered that different operation modes (e.g.,URLLC and eMBB) are operated at the same time pertaining to the samewireless device. Transmission quality may be represented in a priorityrepresentation.

A transmission quality may be indicated explicitly and/or implicitly.Transmission quality may be explicitly indicated with control signaling,e.g. a downlink control information message and/or configured, e.g. withhigher-layer signaling like MAC signaling and/or RRC signaling. In somecases, a DCI message, e.g. a scheduling grant, may indicate and/or pointand/or index to a configured or predefined transmission quality, whichfor example may be one of a set and/or correspond to a table entry. Atransmission quality may for example be implicitly indicated based on acharacteristic of a control information message, e.g. a DCI messageformat (e.g., DCI format 0_n, e.g. 0_0 or 0_1, in an NR system) and/orresource or resource structure (e.g., indicated or allocated by a DCImessage, or configured for a transmission quality) and/or an identityindicated in a DCI message (e.g., a RNTI, which may be used forscrambling the DCI message and/or an associated error coding like aCRC). A wireless device may be configured with different RNTIs for URLLCand/or eMBB or other operation modes.

A predetermined time window (or latency window) may represent a (targetor required, for example) maximum time after a triggering event or time(e.g., start or end of a received DCI or PDSCH transmission) atransmission has to occur to fulfil a latency requirement. The timewindow may also be referred to as latency time window. The window mayrepresent the latency requirement of the transmission with the higherlatency, and/or, in some cases, the latency requirement for thetransmission for which the latency requirement demands an earliertransmission. The predetermined time window may start at the beginningor end of a received transmission (also referred to as referencesignaling or reference transmission), e.g. a scheduling DCI or a subjecttransmission, for example a data transmission like a PDSCH transmissionfor which HARQ feedback transmission is triggered, or a controlinformation transmission like a PDCCH transmission (e.g., DCI)scheduling the PDSCH transmission. Thus, the window may be adapted to atriggering transmission, relative to which the time window (which may bereferred to as latency window) and/or its end in time domain may bearranged or determined. A time window being pre-determined maycorrespond to the size or duration of the time window beingpredetermined, e.g. configured or configurable or predefined, whereasits exact location (e.g., start) may depend on a triggering event likethe reference signaling or transmission.

A resource structure may represent time/frequency resources and mayoptionally also comprise code resource/s. A resource structure may alsobe referred to as resource or transmission resource. A resourcestructure may be scheduled, e.g. with dynamic scheduling, in particularfor transmission on a data channel, for example with a DCI message likea scheduling grant and/or a DCI format 0_n (e.g., 0_0 or 0_1) for NR. Insome cases, a resource structure may be configured, e.g. a configuredgrant for uplink transmission (by a wireless device) on a data channellike PUSCH. A resource structure pertaining to a control channel likePUCCH or another physical channel for control may for example beconfigured by higher layer signaling, e.g. with RRC and/or MACsignaling. A resource structure for a control channel may for example beconfigured as part of a pool or a set. Multiple sets may be configured,e.g. for different payloads and/or different formats for PUCCHtransmission and/or different types of control information to betransmitted. A resource may represent a resource structure and/orcomprise for example time and/or frequency and/or code resources (e.g.,an orthogonal cover code or spreading code). A resource or resourcestructure may cover one or more symbols or symbol time intervals (e.g.,continuously or neighboring symbols) in time domain, and/or one or moresubcarrier or physical resource blocks or physical resource block groupsin frequency domain (e.g., continuously or non-continuously). Resourcesor resource structures may be considered to at least partly or partiallyoverlap in time or time domain, if they comprise a common time interval,e.g. at least one symbol is common to the overlapping resources, forexample at least the ending symbol of one resource and the startingsymbol of the other resource. At least partially or partly overlappingmay be considered to comprise total overlap, e.g. if their time domainextension is identical (e.g., covering the same symbols and the samenumber of symbols), or if one is embedded into the other, e.g. such thatone resource covers at least all the symbols covered by the otherresource (it may cover more symbols, e.g. starting earlier and/or endinglater). Overlapping resources (in time domain) may in some variants bein the same slot, or in some cases in the same subslot. It may generallybe assumed that (different) transmissions of control information may betriggered, e.g. such that multiple PUCCH transmission are triggered orscheduled and/or available or valid (e.g., 2 or more), in a slot orsubslot, for example if different transmissions are for different typesof control information, in particular for different simple types. Forresources overlapping in frequency domain, analogous wording may beused. In general, resources or resource structures at least partly orpartially overlapping in time domain may or may not be at least partlyoverlapping in frequency domain. An allocated resource structure may bea scheduled resource structure, or a configured resource structure.

A transmission on or utilising a resource or resource structure may beconsidered triggered if it is scheduled dynamically, e.g. with ascheduling grant, or a configured resource being indicated fortransmission, e.g., explicitly or implicitly by a control informationmessage like a DCI message. Alternatively, or additionally, atransmission may be considered triggered by a higher layer (e.g., of thetransmitting device, in particular the wireless device), e.g. byproviding data for transmission, e.g. for a scheduled PUSCH resource orto be used for a configured grant. A triggered transmission may pertainto an available resource, and/or a triggered resource may be anavailable resource (available to the wireless device, in particular). Itshould be noted that a triggered transmission does not necessarily haveto be transmitted, or may be transmitted on another resource structurethan the one triggered. A triggered transmission may represent anintended transmission.

A common resource structure may be a resource structure used or suitablefor multiplexing and/or carrying different transmissions and/orinformation and/or information blocks, and/or corresponding signaling. Acommon resource structure may be a scheduled or configured resource. Insome cases, a common resource structure may be a resource structure froma pool or set or sets of configured resources, in particular PUCCHresources. A common resource structure may be indicated in a controlinformation message, or be determined or selected based on whichtransmissions are triggered. It may be considered that a common resourcestructure may be a resource structure from a configured set to which anindicated PUCCH resource belongs. In some cases, it may be from adifferent set of configured PUCCH resources. A common resource structuremay generally be a resource structure that is large enough (e.g., interms of resource elements and/or associated transmission parameters,e.g. MCS) that it can carry the (multiplexed) transmission. Transmissionon a common resource structure may comply with the transmission qualityof one of the multiplexed transmissions, in particular the one of thehigher prioritised transmission (e.g., regarding coding or code rate orMCS or power), or a mixture of the multiplexed transmissions, e.g. suchthat part follows the higher (e.g., regarding coding) and another partthe other. A common resource structure may be a resource structure forwhich transmission is triggered (e.g., if the resource is large enoughto carry multiplexed information), or it may be a different one. Ingeneral, a common resource structure may have an end symbol or end intime that is within a time domain window (latency window), e.g. endsbefore or at the end of the time domain window (e.g., both have the sameending symbol, or the ending symbol of the common resource structureends before or at the end of the window). A common resource structuremay be an available or allocated resource structure, for example ascheduled resource structure or configured resource structure.

Control information transmitted by a wireless device may be uplinkcontrol information, UCI, and/or physical layer information. Controlinformation, in particular UCI, may be one of different types. Exampletypes of control information like UCI may comprise (as simple types)HARQ feedback, measurement information (e.g., CSI type I or II), ascheduling request (e.g., single bit request, or multiple bit request,or buffer report), or beam tracking information. Measurement informationmay be typed in aperiodic (e.g., triggered by dynamic scheduling) andperiodic (e.g., configured to regularly appear). Any two or more of suchtypes may be combined to provide a new (combined) type of controlinformation, e.g. HARQ feedback with SR and/or measurement information,etc.

A control information message may be a physical layer message, e.g. aDCI message or scheduling grant (e.g., format 0, 0_n, e.g. 0_0 or 0_1for NR) or scheduling assignment (e.g., format 1, 1_m, e.g. 1_0 or 1_1for NR). The control information message may be considered to representcontrol signaling.

Transmitting first information and second information (or differentinformation pieces or information blocks) on or utilising one resourcestructure or resource may comprise and/or represent multiplexing.Multiplexing different information or information blocks may compriseerror encoding the information blocks jointly or separately. In somecases, error detection coding may be performed separately on differentinformation blocks, but error correction coding like polar coding orLPDC may be performed on the error detection coded blocks jointly.Multiplexing may comprise rate-matching and/or puncturing, in particularfor multiplexing control information (associated to PUSCH) onto aresource structure for PUSCH. In rate-matching, information bits (andoptionally error detection bits, e.g. CRC bits or parity bits) from theinformation to be multiplexed may be added to information bits (andoptionally error detection bits, e.g. CRC bits or parity bits) beforecoding, in particular before error correction coding. The total numberof coding bits (e.g., for error correction coding) may be adapted toallow for the additional information and/or bits from the informationbits multiplexed on may be dropped. Puncturing may correspond toreplacing encoded modulation symbols of the transmission or informationmultiplexed on by modulation symbols for the multiplexed information ortransmission. Different types of information, in particular controlinformation, may be multiplexed similarly, or differently, e.g.depending on payload size. The resources available for multiplexinginformation onto a resource (which may be intended to carry otherinformation), in particular in case of multiplexing UCI/PUCCHinformation on PUSCH resources or to information on PUSCH, may beindicated and/or based on a scaling factor (also referred to asbeta-factor). Different types of control information may have differentbetas associated to them, e.g. based on configuration. Beta may beconsidered to indicate the resource elements available for UCI, and inrelation to other parameters, e.g. number of bits to multiplex or mapand/or MCS to be used and/or type/s of control information, may indicatethe code rate and/or coding, e.g. the number of coding bits available.

In cases described herein, if no multiplexing is performed, one of thetransmissions (e.g., the one with lower priority/transmission quality)or information or information blocks may be discarded or omitted, orshifted in time, e.g. to a later transmission occasion (e.g., suitableresource), e.g. in a later slot or subslot. Other information may betransmitted on the triggered or scheduled resources.

Information or an information block may in general represent informationor data or bits intended for transmission, e.g. provided by a higherlayer of the transmitting device. Information, in particular aninformation block, may be provided in and/or arranged in and/or compriseand/or represent and/or consist of and/or correspond to a data element,e.g. a transport block and/or data unit (e.g., Packet Data Unit, PDU, inparticular a MAC PDU or higher layer PDU). Different information maycome from different higher-layer units (e.g., MAC entities) and/or maybe associated to different channels (e.g., physical or logical, forexample PUCCH and PUSCH) and/or bearers and/or channel groups (e.g.,logical channel groups) and/or operation modes (e.g., URLLC and eMBB).An information block may be represented by a corresponding informationrepresentation, which may represent the bits of the information block,e.g. based on scrambling and/or modulation and/or mapping and/or codingand/or compression or decompression. An information block may compriseand/or represent higher layer information.

A transmission quality and/or a resource structure may have associatedto it (e.g., via configuration and/or predefined and/or dynamicallyscheduled) one or more transmission parameters, for example pertainingto a modulation and coding scheme (MCS), number of retransmissions ornumber of transmissions in an aggregation and/or in parallel (e.g., forone triggering occurrence), number of layers, transmission power, codingbits to be used (e.g., for error detection and/or error correction),etc. A parameter may define a boundary (e.g., lower boundary for power,or higher boundary for the modulation scheme) or an actual value (e.g.,target or nominal value).

A resource like a resource structure or communication resource (e.g.,transmission resource or reception resource) may be considered availableto the wireless device, if the wireless device is aware or has been madeaware of the resource as potentially useable by it for transmission orreception or communication, e.g. when it is or may be allowed orconfigured or scheduled to use it. A resource may be configured to thewireless device, e.g. with higher layer signaling like RRC signaling orMAC signaling or broadcast signaling, to be available. A resource may beassociated (e.g., by scheduling or configuration) to a type of signalingor channel, e.g. to control signaling or data signaling, and/or to PUCCHor SR or PUSCH. Examples of such may for example be configured resourcesfor control signaling, e.g. a scheduling request, or a configuredresource for data signaling (sometimes also referred to as grant-freeresource, in particular for uplink), e.g. on PUSCH or PDSCH. Aconfigured resource for data signaling may be triggered on or off, e.g.with control signaling, e.g. DCI signaling and/or the controlinformation message. Such resources may be generally referred to asconfigured resources and/or be considered to be semi-static (e.g., untilreconfigured with higher-layer signaling) or semi-persistent resources(e.g., triggered with control signaling). In some cases, a configuredresource may be a resource that is available without needing activationor triggering or scheduling with a control information message, or asemi-persistent resource. Configured resources may in some cases beconsidered to be available over a long and/or undetermined (e.g., at thetime of configuration or scheduling or allocation) timeframe or timeinterval, e.g. longer than one slot, or longer than M slots (M>1 and/orconfigurable), and/or until a change in setup occurs or a specific eventoccurs, e.g. reconfiguration (on higher-layer, e.g. RRC or MAC) ortriggered off (e.g., with control signaling like DCI or SCI, inparticular for semi-persistent). A CORESET for reception of controlsignaling like PDCCH signaling or DCI signaling (or a search space forcontrol signaling) may be considered a configured resource in someexamples. Alternatively, a resource available to a wireless device may aresource scheduled or allocated with control signaling, in particularphysical layer signaling like DCI signaling, e.g. the controlinformation message. Such resources may be referred to as (dynamically)scheduled resources. Scheduled resources may for example comprisedynamically scheduled resources for data signaling, e.g. on PUSCH orPDSCH (for example, according to Type A or Type B scheduling in NR), orresources for control signaling indicated in control signaling, e.g. DCIor SCI, for example PUCCH resources (e.g., one of a set or pool ofresources indicated in the signaling, e.g. a PRI, PUCCH resourceindicator). In some cases, scheduled resources may generally beconsidered resources available or valid for a short (e.g., one slot orseveral slots, e.g. 16 or fewer slots, or 1 frame) or specific ordetermined (e.g., at the time of scheduling or allocation) time frame ortime interval or duration, e.g. a slot (or more than one slot, e.g. forscheduled aggregation). A resource or resource structure available orscheduled for transmission may be considered a transmission resource ortransmission resource structure. In general, transmission utilising aresource or resource structure may cover the resource structure partlyor fully, e.g. using only a part or all of the resource elements of theresource structure. It may be generally considered that a resourcestructure may be logically addressable by control signaling as a unit,and/or may be configured jointly or as a unit, and/or representneighbouring and/or consecutive resource elements (e.g., in time and/orfrequency space, and/or physically or virtually, e.g. if virtualresource allocation is utilised).

Receiving on a common resource structure may comprise monitoring theresource structure and/or associating signaling received thereon with atransmitting device and/or channel and/or operation mode. Receiving maycomprise modulating and/or decoding, e.g. based on information regardingthe (assumed) transmitter, for example the configuration of thistransmitter.

Communication signaling may be data signaling or control signaling (orcomprise both in some cases, e.g. if control and data signaling aremultiplexed, for example if UCI is multiplexed on PUSCH). Communicationsignaling may be of different types and/or priority, e.g. associated toURLLC or eMBB, or associated to logical channel groups. In general, todifferent resources there may be associated the same type of signaling,or different types of signaling, e.g. types of control signaling (e.g.,URLLC or eMBB, and/or HARQ feedback or SR) or data signaling (e.g.,URLLC or eMBB).

Control signaling may carry and/or represent and/or comprise controlinformation, which may be in a control information message. Controlinformation like UCI may generally comprise one or more types of controlinformation, which types may comprise HARQ feedback and/or measurementreport information and/or scheduling request and/or beam-relatedinformation. Control information like DCI may comprise for examplescheduling information or allocation information (e.g., indicatingresource allocation) and/or HARQ process information and/or powercontrol information (e.g., Transmit Power Control command), and/orinformation indicating a bandwidth part to use, etc. The structure(e.g., bit fields) of a control information message may be predefined,e.g. based on the format (e.g., DCI 0_0 or 1_0 for NR), or configured orconfigurable (e.g., DCI 0_1 or 1_1 for NR).

It may be considered that a or each resource is associated to a specifictype of signaling or type of transmission or priority, e.g. byconfiguration or other association. For example, a resource (e.g., firsttransmission resource) for PUSCH or PUCCH may be associated to URLLCoperation, which might have a higher priority than eMBB, to which thesecond transmission resource may be associated. By indicating whichresource is to be used, the associated signaling and/or priority may beindicated. A first transmission/communication/reception resource mayalso be referred to as first resource, a secondtransmission/communication/reception resource may be referred to assecond resource. Different resource may differ in extension in timedomain and/or frequency domain and/or code and/or associated channeland/or type of signaling and/or format of transmission (e.g., PUCCH/UCIformat or DCI/PDCCH format). In general, different types of signalingmay differ regarding control or data signaling, and/or types of controlsignaling (e.g., content, like SR or HARQ feedback or measurementreport) and/or format of transmission. Type of signaling or transmissionformat may be associated to a resource, e.g. according to configuration.For example, to a PUCCH resource or resource set, one or more possiblePUCCH formats may be configured. In general, which PUCCH resource to useout of a set, may be associated to a payload size of information to betransmitted. Thus, a resource (e.g., first or second resource) may bedependent on payload size if control signaling is to be transmitted.

A priority or type of transmission or transmission quality may beassociated to and/or determined based on a signaling characteristic of acontrol information message. The signaling characteristic may compriseone or more characteristics. Example characteristics may comprisemessage format (e.g., 0_1, 0_0, 1_0 1_1, 0_n or 0_m or similar), messagesize (e.g., in bits and/or resource elements) and/or aggregation level(e.g., how over it is repeated) and/or resources in which it is received(e.g., CORESET and/or search space) and/or an identity or addressee ofthe message, e.g. indicated by an identifier like a scrambling code(e.g., RNTI, with which error detection coding or CRC associated to themessage may be scrambled to identify an addressee). For example, anURLLC RNTI may be used to identify that an associated resource is to beused, or an eMBB RNTI analogously. Different formats and/orcharacteristics may be associated to different resources (e.g., on aone-to-one basis), such that the format or resource or RNTI may indicatewhich resource to use.

Alternatively, or additionally, a transmission type or priority ortransmission quality may be based on the content of the controlinformation message, e.g. a bit pattern of a bit field in the controlinformation message and/or an indicator in the control informationmessage, which may represent a priority indicator. The bit field maycomprise one or more bits, e.g. one of one, two or three bits.

In some cases, a resource structure like a first resource structureand/or a second resource structure may be considered scheduled fortransmission and/or available to the wireless device by being scheduledor dynamically scheduled to the wireless device, e.g. with the controlinformation message, and/or may be a scheduled resource. It may beconsidered that a resource structure like a first resource structureand/or a second resource structure may be available and/or scheduled tothe wireless device by being configured to the wireless device and/or isa configured resource. A configured resource may be associated to datasignaling, or to control signaling, in particular to SR signaling.

In some variants, a first resource structure may be a scheduledresource, and a second resource structure may be a configured resource,or vice versa. A control information message may indicate theprioritised one of the resources, e.g. the configured resource if it isa grant-free resource for transmitting data signaling, or the scheduleresource, e.g. if the scheduled resource starts or ends earlier than theconfigured resource, e.g. to lower latency. However, other use cases maybe considered. In some cases, both first resource structure and secondresource structure may be scheduled, or configured.

Communication signaling may in general comprise control signaling and/ordata signaling. The type of signaling may be indicated with a controlinformation message, e.g. indicated by its type and/or content and/orformat, and/or may be associated to the resource determined ascommunication/transmission resource. Accordingly, the approaches may beapplied to a wide variety of use cases.

In particular, it may be considered that the information or type ofsignaling transmitted with the communication signaling is dependent onthe transmission resource and/or the received control informationmessage. The information may be associated to control plane or userplane, and/or a (e.g., physical) channel, and/or to a type of signaling,and/or format of transmission, and/or a logical channel or logicalchannel group and/or priority or priority level, e.g. based on theresource it is associated to and/or a configuration. It may beconsidered that with the control information message, a priorityconfiguration may be overridden, e.g. such that a resource configured(at a higher layer) to be associated to a lower priority level may beprioritised over a resource of a higher priority level. Thus, dynamicre-prioritisation or overriding of prioritisation is possible.

It may be considered that he first transmission resource is associatedto transmission of control information and/or the second transmissionresource is associated to transmission of control information. Theresources may be associated to different types of control information.

In general, a first transmission resource and a second transmissionresource may be associated to different types of signaling and/ordifferent types of control signaling or data signaling and/ortransmission quality or priority (in particular, regarding priority orquality of service, e.g. URLLC or eMBB).

It may be considered that a control information message (e.g., DCImessage) indicates a prioritisation of the first transmission resourcerelative to the second transmission resource, which may for exampleoverride a higher-level prioritisation, e.g. a configured priorityand/or quality of service priority (e.g., URLLC or eMBB).

FIG. 2 schematically shows a radio node or wireless device, inparticular a terminal 10 or a UE (User Equipment). Radio node 10comprises processing circuitry (which may also be referred to as controlcircuitry) 20, which may comprise a controller connected to a memory.Any module of the radio node 10, e.g. a communicating module ordetermining module, may be implemented in and/or executable by, theprocessing circuitry 20, in particular as module in the controller.Radio node 10 also comprises radio circuitry 22 providing receiving andtransmitting or transceiving functionality (e.g., one or moretransmitters and/or receivers and/or transceivers), the radio circuitry22 being connected or connectable to the processing circuitry. Anantenna circuitry 24 of the radio node 10 is connected or connectable tothe radio circuitry 22 to collect or send and/or amplify signals. Radiocircuitry 22 and the processing circuitry 20 controlling it areconfigured for cellular communication with a network, e.g. a RAN asdescribed herein, and/or for sidelink communication. Radio node 10 maygenerally be adapted to carry out any of the methods of operating aradio node like terminal or UE disclosed herein; in particular, it maycomprise corresponding circuitry, e.g. processing circuitry, and/ormodules, e.g. software modules. It may be considered that the radio node10 comprises, and/or is connected or connectable, to a power supply.

FIG. 3 schematically shows a radio node 100, which may in particular beimplemented as a network node 100, for example an eNB or gNB or similarfor NR. Radio node 100 comprises processing circuitry (which may also bereferred to as control circuitry) 120, which may comprise a controllerconnected to a memory. Any module, e.g. transmitting module and/orreceiving module and/or configuring module of the node 100 may beimplemented in and/or executable by the processing circuitry 120. Theprocessing circuitry 120 is connected to control radio circuitry 122 ofthe node 100, which provides receiver and transmitter and/or transceiverfunctionality (e.g., comprising one or more transmitters and/orreceivers and/or transceivers). An antenna circuitry 124 may beconnected or connectable to radio circuitry 122 for signal reception ortransmittance and/or amplification. Node 100 may be adapted to carry outany of the methods for operating a radio node or network node disclosedherein; in particular, it may comprise corresponding circuitry, e.g.processing circuitry, and/or modules. The antenna circuitry 124 may beconnected to and/or comprise an antenna array. The node 100,respectively its circuitry, may be adapted to perform any of the methodsof operating a network node or a radio node as described herein; inparticular, it may comprise corresponding circuitry, e.g. processingcircuitry, and/or modules. The radio node 100 may generally comprisecommunication circuitry, e.g. for communication with another networknode, like a radio node, and/or with a core network and/or an internetor local net, in particular with an information system, which mayprovide information and/or data to be transmitted to a user equipment.

Allocated or scheduled resources may be allocated dynamically, e.g. witha scheduling grant and/or DCI signaling, e.g. DCI format 0_0 or 0_1message (or, if Downlink resources, with a scheduling assignment, e.g. aDCI format 1_0 or 1_1 message), or allocated semi-statically, e.g. witha configured grant and/or RRC signaling. The allocated resources mayrepresent a block of resource elements in time/frequency domain, whichmay be contiguous in time and/or frequency, e.g. for a physicalallocation or a virtual allocation. The resources may be allocated for adata channel, in particular a PUSCH or PSSCH, e.g. based on the formatand/or parametrisation of DCI message used for allocation, or the RRCparametrisation used for a configured grant. In general, a schedulingassignment may schedule subject signaling (e.g., data signaling onPDSCH) to which the acknowledgement signaling or part of it pertains,and may also indicate in which slot the acknowledgementinformation/signaling is expected. A grant may indicate allocatedresources (in particular, for PUSCH) on which uplink transmission mayoccur. If these allocated resources are in a slot indicated foracknowledgment signaling, the acknowledgment signaling may betransmitted using the allocated resources instead of resources allocatedfor control signaling, e.g. PUCCH resources (“UCI on PUSCH” or “HARQ onPUSCH”).

Allocated resources may be resources allocated for a Physical UplinkShared Channel, PUSCH, or a Physical Downlink Channel, PDSCH, or acontrol channel, e.g. PUCCH. The resources may in particular betime/frequency resources, e.g. one or more PRBs or PRB groups on one ormore symbols of a slot. The allocated resources may correspond toslot-based allocation (Type A) or mini-slot based allocation (Type B).

Transmitting acknowledgement signaling may in general be based on and/orin response to subject transmission, and/or to control signalingscheduling subject transmission. Such control signaling and/or subjectsignaling may be transmitted by the signaling radio node, and/or a nodeassociated to it, e.g. in a dual connectivity scenario.

A signaling characteristic may be based on a type or format of ascheduling grant and/or scheduling assignment, and/or type ofallocation, and/or timing of acknowledgement signaling and/or thescheduling grant and/or scheduling assignment, and/or resourcesassociated to acknowledgement signaling and/or the scheduling grantand/or scheduling assignment. For example, if a specific format for ascheduling grant (scheduling or allocating the allocated resources) orscheduling assignment (scheduling the subject transmission foracknowledgement signaling) is used or detected, the first or secondcommunication resource may be used. Type of allocation may pertain todynamic allocation (e.g., using DCI/PDCCH) or semi-static allocation(e.g., for a configured grant). Timing of acknowledgement signaling maypertain to a slot and/or symbol/s the signaling is to be transmitted.Resources used for acknowledgement signaling may pertain to theallocated resources. Timing and/or resources associated to a schedulinggrant or assignment may represent a search space or CORESET (a set ofresources configured for reception of PDCCH transmissions) in which thegrant or assignment is received. Thus, which transmission resource to beused may be based on implicit conditions, requiring low signalingoverhead.

Scheduling may comprise indicating, e.g. with control signaling like DCIor SCI signaling and/or signaling on a control channel like PDCCH orPSCCH, one or more scheduling opportunities of a configuration intendedto carry data signaling or subject signaling. The configuration may berepresented or representable by, and/or correspond to, a table. Ascheduling assignment may for example point to an opportunity of thereception allocation configuration, e.g. indexing a table of schedulingopportunities. In some cases, a reception allocation configuration maycomprise 15 or 16 scheduling opportunities. The configuration may inparticular represent allocation in time. It may be considered that thereception allocation configuration pertains to data signaling, inparticular on a physical data channel like PDSCH or PSSCH. In general,the reception allocation configuration may pertain to downlinksignaling, or in some scenarios to sidelink signaling. Control signalingscheduling subject transmission like data signaling may point and/orindex and/or refer to and/or indicate a scheduling opportunity of thereception allocation configuration. It may be considered that thereception allocation configuration is configured or configurable withhigher-layer signaling, e.g. RRC or MAC layer signaling. The receptionallocation configuration may be applied and/or applicable and/or validfor a plurality of transmission timing intervals, e.g. such that foreach interval, one or more opportunities may be indicated or allocatedfor data signaling. These approaches allow efficient and flexiblescheduling, which may be semi-static, but may updated or reconfigured onuseful timescales in response to changes of operation conditions.

Control information, e.g., in a control information message, in thiscontext may in particular be implemented as and/or represented by ascheduling assignment, which may indicate subject transmission forfeedback (transmission of acknowledgement signaling), and/or reportingtiming and/or frequency resources and/or code resources. Reportingtiming may indicate a timing for scheduled acknowledgement signaling,e.g. slot and/or symbol and/or resource set. Control information may becarried by control signaling.

Subject transmissions may comprise one or more individual transmissions.Scheduling assignments may comprise one or more scheduling assignments.It should generally be noted that in a distributed system, subjecttransmissions, configuration and/or scheduling may be provided bydifferent nodes or devices or transmission points. Different subjecttransmissions may be on the same carrier or different carriers (e.g., ina carrier aggregation), and/or same or different bandwidth parts, and/oron the same or different layers or beams, e.g. in a MIMO scenario,and/or to same or different ports. Generally, subject transmissions maypertain to different HARQ processes (or different sub-processes, e.g. inMIMO with different beams/layers associated to the same processidentifier, but different sub-process-identifiers like swap bits). Ascheduling assignment and/or a HARQ codebook may indicate a target HARQstructure. A target HARQ structure may for example indicate an intendedHARQ response to a subject transmission, e.g. the number of bits and/orwhether to provide code block group level response or not. However, itshould be noted that the actual structure used may differ from thetarget structure, e.g. due to the total size of target structures for asubpattern being larger than the predetermined size.

Transmitting acknowledgement signaling, also referred to as transmittingacknowledgement information or feedback information or simply as HARQfeedback or feedback or reporting feedback, may comprise, and/or bebased on determining correct or incorrect reception of subjecttransmission/s, e.g. based on error coding and/or based on schedulingassignment/s scheduling the subject transmissions. Transmittingacknowledgement information may be based on, and/or comprise, astructure for acknowledgement information to transmit, e.g. thestructure of one or more subpatterns, e.g. based on which subjecttransmission is scheduled for an associated subdivision. Transmittingacknowledgement information may comprise transmitting correspondingsignaling, e.g. at one instance and/or in one message and/or onechannel, in particular a physical channel, which may be a controlchannel. In some cases, the channel may be a shared channel or datachannel, e.g. utilising rate-matching of the acknowledgment information.The acknowledgement information may generally pertain to a plurality ofsubject transmissions, which may be on different channels and/orcarriers, and/or may comprise data signaling and/or control signaling.The acknowledgment information may be based on a codebook, which may bebased on one or more size indications and/or assignment indications(representing HARQ structures), which may be received with a pluralityof control signalings and/or control messages, e.g. in the same ordifferent transmission timing structures, and/or in the same ordifferent (target) sets of resources. Transmitting acknowledgementinformation may comprise determining the codebook, e.g. based on controlinformation in one or more control information messages and/or aconfiguration. A codebook may pertain to transmitting acknowledgementinformation at a single and/or specific instant, e.g. a single PUCCH orPUSCH transmission, and/or in one message or with jointly encoded and/ormodulated acknowledgement information. Generally, acknowledgmentinformation may be transmitted together with other control information,e.g. a scheduling request and/or measurement information.

Acknowledgement signaling may in some cases comprise, next toacknowledgement information, other information, e.g. controlinformation, in particular, uplink or sidelink control information, likea scheduling request and/or measurement information, or similar, and/orerror detection and/or correction information, respectively associatedbits. The payload size of acknowledgement signaling may represent thenumber of bits of acknowledgement information, and/or in some cases thetotal number of bits carried by the acknowledgement signaling, and/orthe number of resource elements needed.

Subject transmission may be data signaling or control signaling. Thetransmission may be on a shared or dedicated channel. Data signaling maybe on a data channel, for example on a PDSCH or PSSCH, or on a dedicateddata channel, e.g. for low latency and/or high reliability, e.g. a URLLCchannel. Control signaling may be on a control channel, for example on acommon control channel or a PDCCH or PSCCH, and/or comprise one or moreDCI messages or SCI messages. In some cases, the subject transmissionmay comprise, or represent, reference signaling. For example, it maycomprise DM-RS and/or pilot signaling and/or discovery signaling and/orsounding signaling and/or phase tracking signaling and/or cell-specificreference signaling and/or user-specific signaling, in particularCSI-RS. A subject transmission may pertain to one scheduling assignmentand/or one acknowledgement signaling process (e.g., according toidentifier or subidentifier), and/or one subdivision. In some cases, asubject transmission may cross the borders of subdivisions in time, e.g.due to being scheduled to start in one subdivision and extending intoanother, or even crossing over more than one subdivision. In this case,it may be considered that the subject transmission is associated to thesubdivision it ends in.

It may be considered that transmitting acknowledgement information, inparticular of acknowledgement information, is based on determiningwhether the subject transmission/s has or have been received correctly,e.g. based on error coding and/or reception quality. Reception qualitymay for example be based on a determined signal quality. Acknowledgementinformation may generally be transmitted to a signaling radio nodeand/or node arrangement and/or to a network and/or network node.

Acknowledgement information, or bit/s of a subpattern structure of suchinformation (e.g., an acknowledgement information structure, mayrepresent and/or comprise one or more bits, in particular a pattern ofbits. Multiple bits pertaining to a data structure or substructure ormessage like a control message may be considered a subpattern. Thestructure or arrangement of acknowledgement information may indicate theorder, and/or meaning, and/or mapping, and/or pattern of bits (orsubpatterns of bits) of the information. The structure or mapping may inparticular indicate one or more data block structures, e.g. code blocksand/or code block groups and/or transport blocks and/or messages, e.g.command messages, the acknowledgement information pertains to, and/orwhich bits or subpattern of bits are associated to which data blockstructure. In some cases, the mapping may pertain to one or moreacknowledgement signaling processes, e.g. processes with differentidentifiers, and/or one or more different data streams. Theconfiguration or structure or codebook may indicate to which process/esand/or data stream/s the information pertains. Generally, theacknowledgement information may comprise one or more subpatterns, eachof which may pertain to a data block structure, e.g. a code block orcode block group or transport block. A subpattern may be arranged toindicate acknowledgement or non-acknowledgement, or anotherretransmission state like non-scheduling or non-reception, of theassociated data block structure. It may be considered that a subpatterncomprises one bit, or in some cases more than one bit. It should benoted that acknowledgement information may be subjected to significantprocessing before being transmitted with acknowledgement signaling.Different configurations may indicate different sizes and/or mappingand/or structures and/or pattern.

An acknowledgment signaling process (providing acknowledgmentinformation) may be a HARQ process, and/or be identified by a processidentifier, e.g. a HARQ process identifier or subidentifier.Acknowledgement signaling and/or associated acknowledgement informationmay be referred to as feedback or acknowledgement feedback. It should benoted that data blocks or structures to which subpatterns may pertainmay be intended to carry data (e.g., information and/or systemic and/orcoding bits). However, depending on transmission conditions, such datamay be received or not received (or not received correctly), which maybe indicated correspondingly in the feedback. In some cases, asubpattern of acknowledgement signaling may comprise padding bits, e.g.if the acknowledgement information for a data block requires fewer bitsthan indicated as size of the subpattern. Such may for example happen ifthe size is indicated by a unit size larger than required for thefeedback.

Acknowledgment information may generally indicate at least ACK or NACK,e.g. pertaining to an acknowledgment signaling process, or an element ofa data block structure like a data block, subblock group or subblock, ora message, in particular a control message. Generally, to anacknowledgment signaling process there may be associated one specificsubpattern and/or a data block structure, for which acknowledgmentinformation may be provided. Acknowledgement information may comprise aplurality of pieces of information, represented in a plurality of HARQstructures.

An acknowledgment signaling process may determine correct or incorrectreception, and/or corresponding acknowledgement information, of a datablock like a transport block, and/or substructures thereof, based oncoding bits associated to the data block, and/or based on coding bitsassociated to one or more data block and/or subblocks and/or subblockgroup/s. Acknowledgement information (determined by an acknowledgementsignaling process) may pertain to the data block as a whole, and/or toone or more subblocks or subblock groups. A code block may be consideredan example of a subblock, whereas a code block group may be consideredan example of a subblock group. Accordingly, the associated subpatternmay comprise one or more bits indicating reception status or feedback ofthe data block, and/or one or more bits indicating reception status orfeedback of one or more subblocks or subblock groups. Each subpattern orbit of the subpattern may be associated and/or mapped to a specific datablock or subblock or subblock group. In some variants, correct receptionfor a data block may be indicated if all subblocks or subblock groupsare correctly identified. In such a case, the subpattern may representacknowledgement information for the data block as a whole, reducingoverhead in comparison to provide acknowledgement information for thesubblocks or subblock groups. The smallest structure (e.g.subblock/subblock group/data block) the subpattern providesacknowledgement information for and/or is associated to may beconsidered its (highest) resolution. In some variants, a subpattern mayprovide acknowledgment information regarding several elements of a datablock structure and/or at different resolution, e.g. to allow morespecific error detection. For example, even if a subpattern indicatesacknowledgment signaling pertaining to a data block as a whole, in somevariants higher resolution (e.g., subblock or subblock group resolution)may be provided by the subpattern. A subpattern may generally compriseone or more bits indicating ACK/NACK for a data block, and/or one ormore bits for indicating ACK/NACK for a subblock or subblock group, orfor more than one subblock or subblock group.

A subblock and/or subblock group may comprise information bits(representing the data to be transmitted, e.g. user data and/ordownlink/sidelink data or uplink data). It may be considered that a datablock and/or subblock and/or subblock group also comprises error one ormore error detection bits, which may pertain to, and/or be determinedbased on, the information bits (for a subblock group, the errordetection bit/s may be determined based on the information bits and/orerror detection bits and/or error correction bits of the subblock/s ofthe subblock group). A data block or substructure like subblock orsubblock group may comprise error correction bits, which may inparticular be determined based on the information bits and errordetection bits of the block or substructure, e.g. utilising an errorcorrection coding scheme, e.g. LDPC or polar coding. Generally, theerror correction coding of a data block structure (and/or associatedbits) may cover and/or pertain to information bits and error detectionbits of the structure. A subblock group may represent a combination ofone or more code blocks, respectively the corresponding bits. A datablock may represent a code block or code block group, or a combinationof more than one code block groups. A transport block may be split up incode blocks and/or code block groups, for example based on the bit sizeof the information bits of a higher layer data structure provided forerror coding and/or size requirements or preferences for error coding,in particular error correction coding. Such a higher layer datastructure is sometimes also referred to as transport block, which inthis context represents information bits without the error coding bitsdescribed herein, although higher layer error handling information maybe included, e.g. for an internet protocol like TCP. However, such errorhandling information represents information bits in the context of thisdisclosure, as the acknowledgement signaling procedures described treatit accordingly.

In some variants, a subblock like a code block may comprise errorcorrection bits, which may be determined based on the information bit/sand/or error detection bit/s of the subblock. An error correction codingscheme may be used for determining the error correction bits, e.g. basedon LDPC or polar coding or Reed-Mueller coding. In some cases, asubblock or code block may be considered to be defined as a block orpattern of bits comprising information bits, error detection bit/sdetermined based on the information bits, and error correction bit/sdetermined based on the information bits and/or error detection bit/s.It may be considered that in a subblock, e.g. code block, theinformation bits (and possibly the error correction bit/s) are protectedand/or covered by the error correction scheme or corresponding errorcorrection bit/s. A code block group may comprise one or more codeblocks. In some variants, no additional error detection bits and/orerror correction bits are applied, however, it may be considered toapply either or both. A transport block may comprise one or more codeblock groups. It may be considered that no additional error detectionbits and/or error correction bits are applied to a transport block,however, it may be considered to apply either or both. In some specificvariants, the code block group/s comprise no additional layers of errordetection or correction coding, and the transport block may compriseonly additional error detection coding bits, but no additional errorcorrection coding. This may particularly be true if the transport blocksize is larger than the code block size and/or the maximum size forerror correction coding. A subpattern of acknowledgement signaling (inparticular indicating ACK or NACK) may pertain to a code block, e.g.indicating whether the code block has been correctly received. It may beconsidered that a subpattern pertains to a subgroup like a code blockgroup or a data block like a transport block. In such cases, it mayindicate ACK, if all subblocks or code blocks of the group ordata/transport block are received correctly (e.g. based on a logical ANDoperation), and NACK or another state of non-correct reception if atleast one subblock or code block has not been correctly received. Itshould be noted that a code block may be considered to be correctlyreceived not only if it actually has been correctly received, but alsoif it can be correctly reconstructed based on soft-combining and/or theerror correction coding.

A subpattern/HARQ structure may pertain to one acknowledgement signalingprocess and/or one carrier like a component carrier and/or data blockstructure or data block. It may in particular be considered that one(e.g. specific and/or single) subpattern pertains, e.g. is mapped by thecodebook, to one (e.g., specific and/or single) acknowledgementsignaling process, e.g. a specific and/or single HARQ process. It may beconsidered that in the bit pattern, subpatterns are mapped toacknowledgement signaling processes and/or data blocks or data blockstructures on a one-to-one basis. In some variants, there may bemultiple subpatterns (and/or associated acknowledgment signalingprocesses) associated to the same component carrier, e.g. if multipledata streams transmitted on the carrier are subject to acknowledgementsignaling processes. A subpattern may comprise one or more bits, thenumber of which may be considered to represent its size or bit size.Different bit n-tupels (n being 1 or larger) of a subpattern may beassociated to different elements of a data block structure (e.g., datablock or subblock or subblock group), and/or represent differentresolutions. There may be considered variants in which only oneresolution is represented by a bit pattern, e.g. a data block. A bitn-tupel may represent acknowledgement information (also referred to afeedback), in particular ACK or NACK, and optionally, (if n>1), mayrepresent DTX/DRX or other reception states. ACK/NACK may be representedby one bit, or by more than one bit, e.g. to improve disambiguity of bitsequences representing ACK or NACK, and/or to improve transmissionreliability.

The acknowledgement information or feedback information may pertain to aplurality of different transmissions, which may be associated to and/orrepresented by data block structures, respectively the associated datablocks or data signaling. The data block structures, and/or thecorresponding blocks and/or signaling, may be scheduled for simultaneoustransmission, e.g. for the same transmission timing structure, inparticular within the same slot or subframe, and/or on the samesymbol/s. However, alternatives with scheduling for non-simultaneoustransmission may be considered. For example, the acknowledgmentinformation may pertain to data blocks scheduled for differenttransmission timing structures, e.g. different slots (or mini-slots, orslots and mini-slots) or similar, which may correspondingly be received(or not or wrongly received). Scheduling signaling may generallycomprise indicating resources, e.g. time and/or frequency resources, forexample for receiving or transmitting the scheduled signaling.

References to specific resource structures like transmission timingstructure and/or symbol and/or slot and/or mini-slot and/or subcarrierand/or carrier may pertain to a specific numerology, which may bepredefined and/or configured or configurable. A transmission timingstructure may represent a time interval, which may cover one or moresymbols. Some examples of a transmission timing structure aretransmission time interval (TTI), subframe, slot, subslot, andmini-slot. A slot may comprise a predetermined, e.g. predefined and/orconfigured or configurable, number of symbols, e.g. 6 or 7, or 12 or 14.A subslot may be (e.g., a configurable or configured or predefined)sub-unit or division of a slot, which may comprise a subset of thesymbols in the slot, e.g. consecutive and/or neighbouring symbols. Amini-slot may comprise a number of symbols (which may in particular beconfigurable or configured) smaller than the number of symbols of aslot, in particular 1, 2, 3 or 4 symbols. A transmission timingstructure may cover a time interval of a specific length, which may bedependent on symbol time length and/or cyclic prefix used. Atransmission timing structure may pertain to, and/or cover, a specifictime interval in a time stream, e.g. synchronized for communication.Timing structures used and/or scheduled for transmission, e.g. slotand/or mini-slots, may be scheduled in relation to, and/or synchronizedto, a timing structure provided and/or defined by other transmissiontiming structures. Such transmission timing structures may define atiming grid, e.g., with symbol time intervals within individualstructures representing the smallest timing units. Such a timing gridmay for example be defined by slots or subframes (wherein in some cases,subframes may be considered specific variants of slots). A transmissiontiming structure may have a duration (length in time) determined basedon the durations of its symbols, possibly in addition to cyclicprefix/es used. The symbols of a transmission timing structure may havethe same duration, or may in some variants have different duration. Thenumber of symbols in a transmission timing structure may be predefinedand/or configured or configurable, and/or be dependent on numerology.The timing of a mini-slot may generally be configured or configurable,in particular by the network and/or a network node. The timing may beconfigurable to start and/or end at any symbol of the transmissiontiming structure, in particular one or more slots.

There is generally considered a program product comprising instructionsadapted for causing processing and/or control circuitry to carry outand/or control any method described herein, in particular when executedon the processing and/or control circuitry. Also, there is considered acarrier medium arrangement carrying and/or storing a program product asdescribed herein.

A carrier medium arrangement may comprise one or more carrier media.Generally, a carrier medium may be accessible and/or readable and/orreceivable by processing or control circuitry. Storing data and/or aprogram product and/or code may be seen as part of carrying data and/ora program product and/or code. A carrier medium generally may comprise aguiding/transporting medium and/or a storage medium. Aguiding/transporting medium may be adapted to carry and/or carry and/orstore signals, in particular electromagnetic signals and/or electricalsignals and/or magnetic signals and/or optical signals. A carriermedium, in particular a guiding/transporting medium, may be adapted toguide such signals to carry them. A carrier medium, in particular aguiding/transporting medium, may comprise the electromagnetic field,e.g. radio waves or microwaves, and/or optically transmissive material,e.g. glass fiber, and/or cable. A storage medium may comprise at leastone of a memory, which may be volatile or non-volatile, a buffer, acache, an optical disc, magnetic memory, flash memory, etc.

A system comprising one or more radio nodes as described herein, inparticular a network node and a user equipment, is described. The systemmay be a wireless communication system, and/or provide and/or representa radio access network.

Moreover, there may be generally considered a method of operating aninformation system, the method comprising providing information.Alternatively, or additionally, an information system adapted forproviding information may be considered. Providing information maycomprise providing information for, and/or to, a target system, whichmay comprise and/or be implemented as radio access network and/or aradio node, in particular a network node or user equipment or terminal.Providing information may comprise transferring and/or streaming and/orsending and/or passing on the information, and/or offering theinformation for such and/or for download, and/or triggering suchproviding, e.g. by triggering a different system or node to streamand/or transfer and/or send and/or pass on the information. Theinformation system may comprise, and/or be connected or connectable to,a target, for example via one or more intermediate systems, e.g. a corenetwork and/or internet and/or private or local network. Information maybe provided utilising and/or via such intermediate system/s. Providinginformation may be for radio transmission and/or for transmission via anair interface and/or utilising a RAN or radio node as described herein.Connecting the information system to a target, and/or providinginformation, may be based on a target indication, and/or adaptive to atarget indication. A target indication may indicate the target, and/orone or more parameters of transmission pertaining to the target and/orthe paths or connections over which the information is provided to thetarget. Such parameter/s may in particular pertain to the air interfaceand/or radio access network and/or radio node and/or network node.Example parameters may indicate for example type and/or nature of thetarget, and/or transmission capacity (e.g., data rate) and/or latencyand/or reliability and/or cost, respectively one or more estimatesthereof. The target indication may be provided by the target, ordetermined by the information system, e.g. based on information receivedfrom the target and/or historical information, and/or be provided by auser, for example a user operating the target or a device incommunication with the target, e.g. via the RAN and/or air interface.For example, a user may indicate on a user equipment communicating withthe information system that information is to be provided via a RAN,e.g. by selecting from a selection provided by the information system,for example on a user application or user interface, which may be a webinterface. An information system may comprise one or more informationnodes. An information node may generally comprise processing circuitryand/or communication circuitry. In particular, an information systemand/or an information node may be implemented as a computer and/or acomputer arrangement, e.g. a host computer or host computer arrangementand/or server or server arrangement. In some variants, an interactionserver (e.g., web server) of the information system may provide a userinterface, and based on user input may trigger transmitting and/orstreaming information provision to the user (and/or the target) fromanother server, which may be connected or connectable to the interactionserver and/or be part of the information system or be connected orconnectable thereto. The information may be any kind of data, inparticular data intended for a user of for use at a terminal, e.g. videodata and/or audio data and/or location data and/or interactive dataand/or game-related data and/or environmental data and/or technical dataand/or traffic data and/or vehicular data and/or circumstantial dataand/or operational data. The information provided by the informationsystem may be mapped to, and/or mappable to, and/or be intended formapping to, communication or data signaling and/or one or more datachannels as described herein (which may be signaling or channel/s of anair interface and/or used within a RAN and/or for radio transmission).It may be considered that the information is formatted based on thetarget indication and/or target, e.g. regarding data amount and/or datarate and/or data structure and/or timing, which in particular may bepertaining to a mapping to communication or data signaling and/or a datachannels. Mapping information to data signaling and/or data channel/smay be considered to refer to using the signaling/channel/s to carry thedata, e.g. on higher layers of communication, with thesignaling/channel/s underlying the transmission. A target indicationgenerally may comprise different components, which may have differentsources, and/or which may indicate different characteristics of thetarget and/or communication path/s thereto. A format of information maybe specifically selected, e.g. from a set of different formats, forinformation to be transmitted on an air interface and/or by a RAN asdescribed herein. This may be particularly pertinent since an airinterface may be limited in terms of capacity and/or of predictability,and/or potentially be cost sensitive. The format may be selected to beadapted to the transmission indication, which may in particular indicatethat a RAN or radio node as described herein is in the path (which maybe the indicated and/or planned and/or expected path) of informationbetween the target and the information system. A (communication) path ofinformation may represent the interface/s (e.g., air and/or cableinterfaces) and/or the intermediate system/s (if any), between theinformation system and/or the node providing or transferring theinformation, and the target, over which the information is, or is to be,passed on. A path may be (at least partly) undetermined when a targetindication is provided, and/or the information is provided/transferredby the information system, e.g. if an internet is involved, which maycomprise multiple, dynamically chosen paths. Information and/or a formatused for information may be packet-based, and/or be mapped, and/or bemappable and/or be intended for mapping, to packets. Alternatively, oradditionally, there may be considered a method for operating a targetdevice comprising providing a target indicating to an informationsystem. More alternatively, or additionally, a target device may beconsidered, the target device being adapted for providing a targetindication to an information system. In another approach, there may beconsidered a target indication tool adapted for, and/or comprising anindication module for, providing a target indication to an informationsystem. The target device may generally be a target as described above.A target indication tool may comprise, and/or be implemented as,software and/or application or app, and/or web interface or userinterface, and/or may comprise one or more modules for implementingactions performed and/or controlled by the tool. The tool and/or targetdevice may be adapted for, and/or the method may comprise, receiving auser input, based on which a target indicating may be determined and/orprovided. Alternatively, or additionally, the tool and/or target devicemay be adapted for, and/or the method may comprise, receivinginformation and/or communication signaling carrying information, and/oroperating on, and/or presenting (e.g., on a screen and/or as audio or asother form of indication), information. The information may be based onreceived information and/or communication signaling carryinginformation. Presenting information may comprise processing receivedinformation, e.g. decoding and/or transforming, in particular betweendifferent formats, and/or for hardware used for presenting. Operating oninformation may be independent of or without presenting, and/or proceedor succeed presenting, and/or may be without user interaction or evenuser reception, for example for automatic processes, or target deviceswithout (e.g., regular) user interaction like MTC devices, of forautomotive or transport or industrial use. The information orcommunication signaling may be expected and/or received based on thetarget indication. Presenting and/or operating on information maygenerally comprise one or more processing steps, in particular decodingand/or executing and/or interpreting and/or transforming information.Operating on information may generally comprise relaying and/ortransmitting the information, e.g. on an air interface, which mayinclude mapping the information onto signaling (such mapping maygenerally pertain to one or more layers, e.g. one or more layers of anair interface, e.g. RLC (Radio Link Control) layer and/or MAC layerand/or physical layer/s). The information may be imprinted (or mapped)on communication signaling based on the target indication, which maymake it particularly suitable for use in a RAN (e.g., for a targetdevice like a network node or in particular a UE or terminal). The toolmay generally be adapted for use on a target device, like a UE orterminal. Generally, the tool may provide multiple functionalities, e.g.for providing and/or selecting the target indication, and/or presenting,e.g. video and/or audio, and/or operating on and/or storing receivedinformation. Providing a target indication may comprise transmitting ortransferring the indication as signaling, and/or carried on signaling,in a RAN, for example if the target device is a UE, or the tool for aUE. It should be noted that such provided information may be transferredto the information system via one or more additionally communicationinterfaces and/or paths and/or connections. The target indication may bea higher-layer indication and/or the information provided by theinformation system may be higher-layer information, e.g. applicationlayer or user-layer, in particular above radio layers like transportlayer and physical layer. The target indication may be mapped onphysical layer radio signaling, e.g. related to or on the user-plane,and/or the information may be mapped on physical layer radiocommunication signaling, e.g. related to or on the user-plane (inparticular, in reverse communication directions). The describedapproaches allow a target indication to be provided, facilitatinginformation to be provided in a specific format particularly suitableand/or adapted to efficiently use an air interface. A user input may forexample represent a selection from a plurality of possible transmissionmodes or formats, and/or paths, e.g. in terms of data rate and/orpackaging and/or size of information to be provided by the informationsystem.

In general, a numerology and/or subcarrier spacing may indicate thebandwidth (in frequency domain) of a subcarrier of a carrier, and/or thenumber of subcarriers in a carrier and/or the numbering of thesubcarriers in a carrier. Different numerologies may in particular bedifferent in the bandwidth of a subcarrier. In some variants, all thesubcarriers in a carrier have the same bandwidth associated to them. Thenumerology and/or subcarrier spacing may be different between carriersin particular regarding the subcarrier bandwidth. A symbol time length,and/or a time length of a timing structure pertaining to a carrier maybe dependent on the carrier frequency, and/or the subcarrier spacingand/or the numerology. In particular, different numerologies may havedifferent symbol time lengths.

Signaling may generally comprise one or more symbols and/or signalsand/or messages. A signal may comprise or represent one or more bits. Anindication may represent signaling, and/or be implemented as a signal,or as a plurality of signals. One or more signals may be included inand/or represented by a message. Signaling, in particular controlsignaling, may comprise a plurality of signals and/or messages, whichmay be transmitted on different carriers and/or be associated todifferent signaling processes, e.g. representing and/or pertaining toone or more such processes and/or corresponding information. Anindication may comprise signaling, and/or a plurality of signals and/ormessages and/or may be comprised therein, which may be transmitted ondifferent carriers and/or be associated to different acknowledgementsignaling processes, e.g. representing and/or pertaining to one or moresuch processes. Signaling associated to a channel may be transmittedsuch that represents signaling and/or information for that channel,and/or that the signaling is interpreted by the transmitter and/orreceiver to belong to that channel. Such signaling may generally complywith transmission parameters and/or format/s for the channel.

Reference signaling may be signaling comprising one or more referencesymbols and/or structures. Reference signaling may be adapted forgauging and/or estimating and/or representing transmission conditions,e.g. channel conditions and/or transmission path conditions and/orchannel (or signal or transmission) quality. It may be considered thatthe transmission characteristics (e.g., signal strength and/or formand/or modulation and/or timing) of reference signaling are availablefor both transmitter and receiver of the signaling (e.g., due to beingpredefined and/or configured or configurable and/or being communicated).Different types of reference signaling may be considered, e.g.pertaining to uplink, downlink or sidelink, cell-specific (inparticular, cell-wide, e.g., CRS) or device or user specific (addressedto a specific target or user equipment, e.g., CSI-RS),demodulation-related (e.g., DMRS) and/or signal strength related, e.g.power-related or energy-related or amplitude-related (e.g., SRS or pilotsignaling) and/or phase-related, etc.

An antenna arrangement may comprise one or more antenna elements(radiating elements), which may be combined in antenna arrays. Anantenna array or subarray may comprise one antenna element, or aplurality of antenna elements, which may be arranged e.g. twodimensionally (for example, a panel) or three dimensionally. It may beconsidered that each antenna array or subarray or element is separatelycontrollable, respectively that different antenna arrays arecontrollable separately from each other. A single antennaelement/radiator may be considered the smallest example of a subarray.Examples of antenna arrays comprise one or more multi-antenna panels orone or more individually controllable antenna elements. An antennaarrangement may comprise a plurality of antenna arrays. It may beconsidered that an antenna arrangement is associated to a (specificand/or single) radio node, e.g. a configuring or informing or schedulingradio node, e.g. to be controlled or controllable by the radio node. Anantenna arrangement associated to a UE or terminal may be smaller (e.g.,in size and/or number of antenna elements or arrays) than the antennaarrangement associated to a network node. Antenna elements of an antennaarrangement may be configurable for different arrays, e.g. to change thebeam forming characteristics. In particular, antenna arrays may beformed by combining one or more independently or separately controllableantenna elements or subarrays. The beams may be provided by analogbeamforming, or in some variants by digital beamforming. The informingradio nodes may be configured with the manner of beam transmission, e.g.by transmitting a corresponding indicator or indication, for example asbeam identify indication. However, there may be considered cases inwhich the informing radio node/s are not configured with suchinformation, and/or operate transparently, not knowing the way ofbeamforming used. An antenna arrangement may be considered separatelycontrollable in regard to the phase and/or amplitude/power and/or gainof a signal feed to it for transmission, and/or separately controllableantenna arrangements may comprise an independent or separate transmitand/or receive unit and/or ADC (Analog-Digital-Converter, alternativelyan ADC chain) to convert digital control information into an analogantenna feed for the whole antenna arrangement (the ADC may beconsidered part of, and/or connected or connectable to, antennacircuitry). A scenario in which each antenna element is individuallycontrollable may be referred to as digital beamforming, whereas ascenario in which larger arrays/subarrays are separately controllablemay be considered an example of analog beamforming. Hybrid forms may beconsidered.

Uplink or sidelink signaling may be OFDMA (Orthogonal Frequency DivisionMultiple Access) or SC-FDMA (Single Carrier Frequency Division MultipleAccess) signaling. Downlink signaling may in particular be OFDMAsignaling. However, signaling is not limited thereto (Filter-Bank basedsignaling may be considered one alternative).

A radio node may generally be considered a device or node adapted forwireless and/or radio (and/or microwave) frequency communication, and/orfor communication utilising an air interface, e.g. according to acommunication standard.

A radio node may be a network node, or a user equipment or terminal. Anetwork node may be any radio node of a wireless communication network,e.g. a base station and/or gNodeB (gNB) and/or eNodeB (eNB) and/or relaynode and/or micro/nano/pico/femto node and/or transmission point (TP)and/or access point (AP) and/or other node, in particular for a RAN asdescribed herein.

The terms user equipment (UE) and terminal may be considered to beinterchangeable in the context of this disclosure. A wireless device,user equipment or terminal may represent an end device for communicationutilising the wireless communication network, and/or be implemented as auser equipment according to a standard. Examples of user equipments maycomprise a phone like a smartphone, a personal communication device, amobile phone or terminal, a computer, in particular laptop, a sensor ormachine with radio capability (and/or adapted for the air interface), inparticular for MTC (Machine-Type-Communication, sometimes also referredto M2M, Machine-To-Machine), or a vehicle adapted for wirelesscommunication. A user equipment or terminal may be mobile or stationary.A wireless device generally may comprise, and/or be implemented as,processing circuitry and/or radio circuitry, which may comprise one ormore chips or sets of chips. The circuitry and/or circuitries may bepackaged, e.g. in a chip housing, and/or may have one or more physicalinterfaces to interact with other circuitry and/or for power supply.Such a wireless device may be intended for use in a user equipment orterminal.

A radio node may generally comprise processing circuitry and/or radiocircuitry. A radio node, in particular a network node, may in some casescomprise cable circuitry and/or communication circuitry, with which itmay be connected or connectable to another radio node and/or a corenetwork.

Circuitry may comprise integrated circuitry. Processing circuitry maycomprise one or more processors and/or controllers (e.g.,microcontrollers), and/or ASICs (Application Specific IntegratedCircuitry) and/or FPGAs (Field Programmable Gate Array), or similar. Itmay be considered that processing circuitry comprises, and/or is(operatively) connected or connectable to one or more memories or memoryarrangements. A memory arrangement may comprise one or more memories. Amemory may be adapted to store digital information. Examples formemories comprise volatile and non-volatile memory, and/or Random AccessMemory (RAM), and/or Read-Only-Memory (ROM), and/or magnetic and/oroptical memory, and/or flash memory, and/or hard disk memory, and/orEPROM or EEPROM (Erasable Programmable ROM or Electrically ErasableProgrammable ROM).

Radio circuitry may comprise one or more transmitters and/or receiversand/or transceivers (a transceiver may operate or be operable astransmitter and receiver, and/or may comprise joint or separatedcircuitry for receiving and transmitting, e.g. in one package orhousing), and/or may comprise one or more amplifiers and/or oscillatorsand/or filters, and/or may comprise, and/or be connected or connectableto antenna circuitry and/or one or more antennas and/or antenna arrays.An antenna array may comprise one or more antennas, which may bearranged in a dimensional array, e.g. 2D or 3D array, and/or antennapanels. A remote radio head (RRH) may be considered as an example of anantenna array. However, in some variants, a RRH may be also beimplemented as a network node, depending on the kind of circuitry and/orfunctionality implemented therein.

Communication circuitry may comprise radio circuitry and/or cablecircuitry. Communication circuitry generally may comprise one or moreinterfaces, which may be air interface/s and/or cable interface/s and/oroptical interface/s, e.g. laser-based. Interface/s may be in particularpacket-based. Cable circuitry and/or a cable interfaces may comprise,and/or be connected or connectable to, one or more cables (e.g., opticalfiber-based and/or wire-based), which may be directly or indirectly(e.g., via one or more intermediate systems and/or interfaces) beconnected or connectable to a target, e.g. controlled by communicationcircuitry and/or processing circuitry.

Any one or all of the modules disclosed herein may be implemented insoftware and/or firmware and/or hardware. Different modules may beassociated to different components of a radio node, e.g. differentcircuitries or different parts of a circuitry. It may be considered thata module is distributed over different components and/or circuitries. Aprogram product as described herein may comprise the modules related toa device on which the program product is intended (e.g., a userequipment or network node) to be executed (the execution may beperformed on, and/or controlled by the associated circuitry).

A radio access network may be a wireless communication network, and/or aRadio Access Network (RAN) in particular according to a communicationstandard. A communication standard may in particular a standardaccording to 3GPP and/or 5G, e.g. according to NR or LTE, in particularLTE Evolution.

A wireless communication network may be and/or comprise a Radio AccessNetwork (RAN), which may be and/or comprise any kind of cellular and/orwireless radio network, which may be connected or connectable to a corenetwork. The approaches described herein are particularly suitable for a5G network, e.g. LTE Evolution and/or NR (New Radio), respectivelysuccessors thereof. A RAN may comprise one or more network nodes, and/orone or more terminals, and/or one or more radio nodes. A network nodemay in particular be a radio node adapted for radio and/or wirelessand/or cellular communication with one or more terminals. A terminal maybe any device adapted for radio and/or wireless and/or cellularcommunication with or within a RAN, e.g. a user equipment (UE) or mobilephone or smartphone or computing device or vehicular communicationdevice or device for machine-type-communication (MTC), etc. A terminalmay be mobile, or in some cases stationary. A RAN or a wirelesscommunication network may comprise at least one network node and a UE,or at least two radio nodes. There may be generally considered awireless communication network or system, e.g. a RAN or RAN system,comprising at least one radio node, and/or at least one network node andat least one terminal.

Transmitting in downlink may pertain to transmission from the network ornetwork node to the terminal. Transmitting in uplink may pertain totransmission from the terminal to the network or network node.Transmitting in sidelink may pertain to (direct) transmission from oneterminal to another. Uplink, downlink and sidelink (e.g., sidelinktransmission and reception) may be considered communication directions.In some variants, uplink and downlink may also be used to describedwireless communication between network nodes, e.g. for wireless backhauland/or relay communication and/or (wireless) network communication forexample between base stations or similar network nodes, in particularcommunication terminating at such. It may be considered that backhauland/or relay communication and/or network communication is implementedas a form of sidelink or uplink communication or similar thereto.

Control information or a control information message or correspondingsignaling (control signaling) may be transmitted on a control channel,e.g. a physical control channel, which may be a downlink channel or (ora sidelink channel in some cases, e.g. one UE scheduling another UE).For example, control information/allocation information may be signaledby a network node on PDCCH (Physical Downlink Control Channel) and/or aPDSCH (Physical Downlink Shared Channel) and/or a HARQ-specific channel.Acknowledgement signaling, e.g. as a form of control information orsignaling like uplink control information/signaling, may be transmittedby a terminal on a PUCCH (Physical Uplink Control Channel) and/or PUSCH(Physical Uplink Shared Channel) and/or a HARQ-specific channel.Multiple channels may apply for multi-component/multi-carrier indicationor signaling.

Signaling may generally be considered to represent an electromagneticwave structure (e.g., over a time interval and frequency interval),which is intended to convey information to at least one specific orgeneric (e.g., anyone who might pick up the signaling) target. A processof signaling may comprise transmitting the signaling. Transmittingsignaling, in particular control signaling or communication signaling,e.g. comprising or representing acknowledgement signaling and/orresource requesting information, may comprise encoding and/ormodulating. Encoding and/or modulating may comprise error detectioncoding and/or forward error correction encoding and/or scrambling.Receiving control signaling may comprise corresponding decoding and/ordemodulation. Error detection coding may comprise, and/or be based on,parity or checksum approaches, e.g. CRC (Cyclic Redundancy Check).Forward error correction coding may comprise and/or be based on forexample turbo coding and/or Reed-Muller coding, and/or polar codingand/or LDPC coding (Low Density Parity Check). The type of coding usedmay be based on the channel (e.g., physical channel) the coded signal isassociated to. A code rate may represent the ratio of the number ofinformation bits before encoding to the number of encoded bits afterencoding, considering that encoding adds coding bits for error detectioncoding and forward error correction. Coded bits may refer to informationbits (also called systematic bits) plus coding bits.

Communication signaling may comprise, and/or represent, and/or beimplemented as, data signaling, and/or user plane signaling.Communication signaling may be associated to a data channel, e.g. aphysical downlink channel or physical uplink channel or physicalsidelink channel, in particular a PDSCH (Physical Downlink SharedChannel) or PSSCH (Physical Sidelink Shared Channel). Generally, a datachannel may be a shared channel or a dedicated channel. Data signalingmay be signaling associated to and/or on a data channel.

An indication generally may explicitly and/or implicitly indicate theinformation it represents and/or indicates. Implicit indication may forexample be based on position and/or resource used for transmission.Explicit indication may for example be based on a parametrisation withone or more parameters, and/or one or more index or indices, and/or oneor more bit patterns representing the information. It may in particularbe considered that control signaling as described herein, based on theutilised resource sequence, implicitly indicates the control signalingtype.

A resource element may generally describe the smallest individuallyusable and/or encodable and/or decodable and/or modulatable and/ordemodulatable time-frequency resource, and/or may describe atime-frequency resource covering a symbol time length in time and asubcarrier in frequency. A signal may be allocatable and/or allocated toa resource element. A subcarrier may be a subband of a carrier, e.g. asdefined by a standard. A carrier may define a frequency and/or frequencyband for transmission and/or reception. In some variants, a signal(jointly encoded/modulated) may cover more than one resource elements. Aresource element may generally be as defined by a correspondingstandard, e.g. NR or LTE. As symbol time length and/or subcarrierspacing (and/or numerology) may be different between different symbolsand/or subcarriers, different resource elements may have differentextension (length/width) in time and/or frequency domain, in particularresource elements pertaining to different carriers.

A resource generally may represent a time-frequency and/or coderesource, on which signaling, e.g. according to a specific format, maybe communicated, for example transmitted and/or received, and/or beintended for transmission and/or reception.

A border symbol may generally represent a starting symbol or an endingsymbol for transmitting and/or receiving. A starting symbol may inparticular be a starting symbol of uplink or sidelink signaling, forexample control signaling or data signaling. Such signaling may be on adata channel or control channel, e.g. a physical channel, in particulara physical uplink shared channel (like PUSCH) or a sidelink data orshared channel, or a physical uplink control channel (like PUCCH) or asidelink control channel. If the starting symbol is associated tocontrol signaling (e.g., on a control channel), the control signalingmay be in response to received signaling (in sidelink or downlink), e.g.representing acknowledgement signaling associated thereto, which may beHARQ or ARQ signaling. An ending symbol may represent an ending symbol(in time) of downlink or sidelink transmission or signaling, which maybe intended or scheduled for the radio node or user equipment. Suchdownlink signaling may in particular be data signaling, e.g. on aphysical downlink channel like a shared channel, e.g. a PDSCH (PhysicalDownlink Shared Channel). A starting symbol may be determined based on,and/or in relation to, such an ending symbol.

Configuring a radio node, in particular a terminal or user equipment,may refer to the radio node being adapted or caused or set and/orinstructed to operate according to the configuration. Configuring may bedone by another device, e.g., a network node (for example, a radio nodeof the network like a base station or eNodeB) or network, in which caseit may comprise transmitting configuration data to the radio node to beconfigured. Such configuration data may represent the configuration tobe configured and/or comprise one or more instruction pertaining to aconfiguration, e.g. a configuration for transmitting and/or receiving onallocated resources, in particular frequency resources. A radio node mayconfigure itself, e.g., based on configuration data received from anetwork or network node. A network node may utilise, and/or be adaptedto utilise, its circuitry/ies for configuring. Allocation informationmay be considered a form of configuration data. Configuration data maycomprise and/or be represented by configuration information, and/or oneor more corresponding indications and/or message/s

Generally, configuring may include determining configuration datarepresenting the configuration and providing, e.g. transmitting, it toone or more other nodes (parallel and/or sequentially), which maytransmit it further to the radio node (or another node, which may berepeated until it reaches the wireless device). Alternatively, oradditionally, configuring a radio node, e.g., by a network node or otherdevice, may include receiving configuration data and/or data pertainingto configuration data, e.g., from another node like a network node,which may be a higher-level node of the network, and/or transmittingreceived configuration data to the radio node. Accordingly, determininga configuration and transmitting the configuration data to the radionode may be performed by different network nodes or entities, which maybe able to communicate via a suitable interface, e.g., an X2 interfacein the case of LTE or a corresponding interface for NR. Configuring aterminal may comprise scheduling downlink and/or uplink transmissionsfor the terminal, e.g. downlink data and/or downlink control signalingand/or DCI and/or uplink control or data or communication signaling, inparticular acknowledgement signaling, and/or configuring resourcesand/or a resource pool therefor.

A resource structure may be considered to be neighbored in frequencydomain by another resource structure, if they share a common borderfrequency, e.g. one as an upper frequency border and the other as alower frequency border. Such a border may for example be represented bythe upper end of a bandwidth assigned to a subcarrier n, which alsorepresents the lower end of a bandwidth assigned to a subcarrier n+1. Aresource structure may be considered to be neighbored in time domain byanother resource structure, if they share a common border time, e.g. oneas an upper (or right in the figures) border and the other as a lower(or left in the figures) border. Such a border may for example berepresented by the end of the symbol time interval assigned to a symboln, which also represents the beginning of a symbol time intervalassigned to a symbol n+1.

Generally, a resource structure being neighbored by another resourcestructure in a domain may also be referred to as abutting and/orbordering the other resource structure in the domain.

A resource structure may general represent a structure in time and/orfrequency domain, in particular representing a time interval and afrequency interval. A resource structure may comprise and/or becomprised of resource elements, and/or the time interval of a resourcestructure may comprise and/or be comprised of symbol time interval/s,and/or the frequency interval of a resource structure may compriseand/or be comprised of subcarrier/s. A resource element may beconsidered an example for a resource structure, a slot or mini-slot or aPhysical Resource Block (PRB) or parts thereof may be considered others.A resource structure may be associated to a specific channel, e.g. aPUSCH or PUCCH, in particular resource structure smaller than a slot orPRB.

Examples of a resource structure in frequency domain comprise abandwidth or band, or a bandwidth part. A bandwidth part may be a partof a bandwidth available for a radio node for communicating, e.g. due tocircuitry and/or configuration and/or regulations and/or a standard. Abandwidth part may be configured or configurable to a radio node. Insome variants, a bandwidth part may be the part of a bandwidth used forcommunicating, e.g. transmitting and/or receiving, by a radio node. Thebandwidth part may be smaller than the bandwidth (which may be a devicebandwidth defined by the circuitry/configuration of a device, and/or asystem bandwidth, e.g. available for a RAN). It may be considered that abandwidth part comprises one or more resource blocks or resource blockgroups, in particular one or more PRBs or PRB groups. A bandwidth partmay pertain to, and/or comprise, one or more carriers.

A carrier may generally represent a frequency range or band and/orpertain to a central frequency and an associated frequency interval. Itmay be considered that a carrier comprises a plurality of subcarriers. Acarrier may have assigned to it a central frequency or center frequencyinterval, e.g. represented by one or more subcarriers (to eachsubcarrier there may be generally assigned a frequency bandwidth orinterval). Different carriers may be non-overlapping, and/or may beneighboring in frequency domain.

It should be noted that the term “radio” in this disclosure may beconsidered to pertain to wireless communication in general, and may alsoinclude wireless communication utilising microwave and/or millimeterand/or other frequencies, in particular between 100 MHz or 1 GHz, and100 GHz or 20 or 10 GHz. Such communication may utilise one or morecarriers.

A radio node, in particular a network node or a terminal, may generallybe any device adapted for transmitting and/or receiving radio and/orwireless signals and/or data, in particular communication data, inparticular on at least one carrier. The at least one carrier maycomprise a carrier accessed based on a LBT procedure (which may becalled LBT carrier), e.g., an unlicensed carrier. It may be consideredthat the carrier is part of a carrier aggregate.

Receiving or transmitting on a cell or carrier may refer to receiving ortransmitting utilizing a frequency (band) or spectrum associated to thecell or carrier. A cell may generally comprise and/or be defined by orfor one or more carriers, in particular at least one carrier for ULcommunication/transmission (called UL carrier) and at least one carrierfor DL communication/transmission (called DL carrier). It may beconsidered that a cell comprises different numbers of UL carriers and DLcarriers. Alternatively, or additionally, a cell may comprise at leastone carrier for UL communication/transmission and DLcommunication/transmission, e.g., in TDD-based approaches.

A channel may generally be a logical, transport or physical channel. Achannel may comprise and/or be arranged on one or more carriers, inparticular a plurality of subcarriers. A channel carrying and/or forcarrying control signaling/control information may be considered acontrol channel, in particular if it is a physical layer channel and/orif it carries control plane information. Analogously, a channel carryingand/or for carrying data signaling/user information may be considered adata channel, in particular if it is a physical layer channel and/or ifit carries user plane information. A channel may be defined for aspecific communication direction, or for two complementary communicationdirections (e.g., UL and DL, or sidelink in two directions), in whichcase it may be considered to have two component channels, one for eachdirection. Examples of channels comprise a channel for low latencyand/or high reliability transmission, in particular a channel forUltra-Reliable Low Latency Communication (URLLC), which may be forcontrol and/or data.

In general, a symbol may represent and/or be associated to a symbol timelength, which may be dependent on the carrier and/or subcarrier spacingand/or numerology of the associated carrier. Accordingly, a symbol maybe considered to indicate a time interval having a symbol time length inrelation to frequency domain. A symbol time length may be dependent on acarrier frequency and/or bandwidth and/or numerology and/or subcarrierspacing of, or associated to, a symbol. Accordingly, different symbolsmay have different symbol time lengths. In particular, numerologies withdifferent subcarrier spacings may have different symbol time length.Generally, a symbol time length may be based on, and/or include, a guardtime interval or cyclic extension, e.g. prefix or postfix.

A sidelink may generally represent a communication channel (or channelstructure) between two UEs and/or terminals, in which data istransmitted between the participants (UEs and/or terminals) via thecommunication channel, e.g. directly and/or without being relayed via anetwork node. A sidelink may be established only and/or directly via airinterface/s of the participant, which may be directly linked via thesidelink communication channel. In some variants, sidelink communicationmay be performed without interaction by a network node, e.g. on fixedlydefined resources and/or on resources negotiated between theparticipants. Alternatively, or additionally, it may be considered thata network node provides some control functionality, e.g. by configuringresources, in particular one or more resource pool/s, for sidelinkcommunication, and/or monitoring a sidelink, e.g. for charging purposes.

Sidelink communication may also be referred to as device-to-device (D2D)communication, and/or in some cases as ProSe (Proximity Services)communication, e.g. in the context of LTE. A sidelink may be implementedin the context of V2x communication (Vehicular communication), e.g. V2V(Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure) and/or V2P(Vehicle-to-Person). Any device adapted for sidelink communication maybe considered a user equipment or terminal.

A sidelink communication channel (or structure) may comprise one or more(e.g., physical or logical) channels, e.g. a PSCCH (Physical SidelinkControl CHannel, which may for example carry control information like anacknowledgement position indication, and/or a PSSCH (Physical SidelinkShared CHannel, which for example may carry data and/or acknowledgementsignaling). It may be considered that a sidelink communication channel(or structure) pertains to and/or used one or more carrier/s and/orfrequency range/s associated to, and/or being used by, cellularcommunication, e.g. according to a specific license and/or standard.Participants may share a (physical) channel and/or resources, inparticular in frequency domain and/or related to a frequency resourcelike a carrier) of a sidelink, such that two or more participantstransmit thereon, e.g. simultaneously, and/or time-shifted, and/or theremay be associated specific channels and/or resources to specificparticipants, so that for example only one participant transmits on aspecific channel or on a specific resource or specific resources, e.g.,in frequency domain and/or related to one or more carriers orsubcarriers.

A sidelink may comply with, and/or be implemented according to, aspecific standard, e.g. a LTE-based standard and/or NR. A sidelink mayutilise TDD (Time Division Duplex) and/or FDD (Frequency DivisionDuplex) technology, e.g. as configured by a network node, and/orpreconfigured and/or negotiated between the participants. A userequipment may be considered to be adapted for sidelink communication ifit, and/or its radio circuitry and/or processing circuitry, is adaptedfor utilising a sidelink, e.g. on one or more frequency ranges and/orcarriers and/or in one or more formats, in particular according to aspecific standard. It may be generally considered that a Radio AccessNetwork is defined by two participants of a sidelink communication.Alternatively, or additionally, a Radio Access Network may berepresented, and/or defined with, and/or be related to a network nodeand/or communication with such a node.

Communication or communicating may generally comprise transmittingand/or receiving signaling. Communication on a sidelink (or sidelinksignaling) may comprise utilising the sidelink for communication(respectively, for signaling). Sidelink transmission and/or transmittingon a sidelink may be considered to comprise transmission utilising thesidelink, e.g. associated resources and/or transmission formats and/orcircuitry and/or the air interface. Sidelink reception and/or receivingon a sidelink may be considered to comprise reception utilising thesidelink, e.g. associated resources and/or transmission formats and/orcircuitry and/or the air interface. Sidelink control information (e.g.,SCI) may generally be considered to comprise control informationtransmitted utilising a sidelink. Communicating or signaling may in somecases be based on TDD operation, and in other cases on FDD operation.

Generally, carrier aggregation (CA) may refer to the concept of a radioconnection and/or communication link between a wireless and/or cellularcommunication network and/or network node and a terminal or on asidelink comprising a plurality of carriers for at least one directionof transmission (e.g. DL and/or UL), as well as to the aggregate ofcarriers. A corresponding communication link may be referred to ascarrier aggregated communication link or CA communication link; carriersin a carrier aggregate may be referred to as component carriers (CC). Insuch a link, data may be transmitted over more than one of the carriersand/or all the carriers of the carrier aggregation (the aggregate ofcarriers). A carrier aggregation may comprise one (or more) dedicatedcontrol carriers and/or primary carriers (which may e.g. be referred toas primary component carrier or PCC), over which control information maybe transmitted, wherein the control information may refer to the primarycarrier and other carriers, which may be referred to as secondarycarriers (or secondary component carrier, SCC). However, in someapproaches, control information may be sent over more than one carrierof an aggregate, e.g. one or more PCCs and one PCC and one or more SCCs.

A transmission may generally pertain to a specific channel and/orspecific resources, in particular with a starting symbol and endingsymbol in time, covering the interval therebetween. A scheduledtransmission may be a transmission scheduled and/or expected and/or forwhich resources are scheduled or provided or reserved. However, notevery scheduled transmission has to be realized. For example, ascheduled downlink transmission may not be received, or a scheduleduplink transmission may not be transmitted due to power limitations, orother influences (e.g., a channel on an unlicensed carrier beingoccupied). A transmission may be scheduled for a transmission timingsubstructure (e.g., a mini-slot, and/or covering only a part of atransmission timing structure) within a transmission timing structurelike a slot. A border symbol may be indicative of a symbol in thetransmission timing structure at which the transmission starts or ends.

Predefined in the context of this disclosure may refer to the relatedinformation being defined for example in a standard, and/or beingavailable without specific configuration from a network or network node,e.g. stored in memory, for example independent of being configured.Configured or configurable may be considered to pertain to thecorresponding information being set/configured, e.g. by the network or anetwork node.

A configuration or schedule, like a mini-slot configuration and/orstructure configuration, may schedule transmissions, e.g. for thetime/transmissions it is valid, and/or transmissions may be scheduled byseparate signaling or separate configuration, e.g. separate RRCsignaling and/or downlink control information signaling. Thetransmission/s scheduled may represent signaling to be transmitted bythe device for which it is scheduled, or signaling to be received by thedevice for which it is scheduled, depending on which side of acommunication the device is. It should be noted that downlink controlinformation or specifically DCI signaling may be considered physicallayer signaling, in contrast to higher layer signaling like MAC (MediumAccess Control) signaling or RRC layer signaling. The higher the layerof signaling is, the less frequent/the more time/resource consuming itmay be considered, at least partially due to the information containedin such signaling having to be passed on through several layers, eachlayer requiring processing and handling.

A scheduled transmission, and/or transmission timing structure like amini-slot or slot, may pertain to a specific channel, in particular aphysical uplink shared channel, a physical uplink control channel, or aphysical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and/or maypertain to a specific cell and/or carrier aggregation. A correspondingconfiguration, e.g. scheduling configuration or symbol configuration maypertain to such channel, cell and/or carrier aggregation. It may beconsidered that the scheduled transmission represents transmission on aphysical channel, in particular a shared physical channel, for example aphysical uplink shared channel or physical downlink shared channel. Forsuch channels, semi-persistent configuring may be particularly suitable.

Generally, a configuration may be a configuration indicating timing,and/or be represented or configured with corresponding configurationdata. A configuration may be embedded in, and/or comprised in, a messageor configuration or corresponding data, which may indicate and/orschedule resources, in particular semi-persistently and/orsemi-statically.

A control region of a transmission timing structure may be an intervalin time for intended or scheduled or reserved for control signaling, inparticular downlink control signaling, and/or for a specific controlchannel, e.g. a physical downlink control channel like PDCCH. Theinterval may comprise, and/or consist of, a number of symbols in time,which may be configured or configurable, e.g. by (UE-specific) dedicatedsignaling (which may be single-cast, for example addressed to orintended for a specific UE), e.g. on a PDCCH, or RRC signaling, or on amulticast or broadcast channel. In general, the transmission timingstructure may comprise a control region covering a configurable numberof symbols. It may be considered that in general the border symbol isconfigured to be after the control region in time.

The duration of a symbol (symbol time length or interval) of thetransmission timing structure may generally be dependent on a numerologyand/or carrier, wherein the numerology and/or carrier may beconfigurable. The numerology may be the numerology to be used for thescheduled transmission.

Scheduling a device, or for a device, and/or related transmission orsignaling, may be considered comprising, or being a form of, configuringthe device with resources, and/or of indicating to the device resources,e.g. to use for communicating. Scheduling may in particular pertain to atransmission timing structure, or a substructure thereof (e.g., a slotor a mini-slot, which may be considered a substructure of a slot). Itmay be considered that a border symbol may be identified and/ordetermined in relation to the transmission timing structure even if fora substructure being scheduled, e.g. if an underlying timing grid isdefined based on the transmission timing structure. Signaling indicatingscheduling may comprise corresponding scheduling information and/or beconsidered to represent or contain configuration data indicating thescheduled transmission and/or comprising scheduling information. Suchconfiguration data or signaling may be considered a resourceconfiguration or scheduling configuration. It should be noted that sucha configuration (in particular as single message) in some cases may notbe complete without other configuration data, e.g. configured with othersignaling, e.g. higher layer signaling. In particular, the symbolconfiguration may be provided in addition to scheduling/resourceconfiguration to identify exactly which symbols are assigned to ascheduled transmission. A scheduling (or resource) configuration mayindicate transmission timing structure/s and/or resource amount (e.g.,in number of symbols or length in time) for a scheduled transmission.

A scheduled transmission may be transmission scheduled, e.g. by thenetwork or network node. Transmission may in this context may be uplink(UL) or downlink (DL) or sidelink (SL) transmission. A device, e.g. auser equipment, for which the scheduled transmission is scheduled, mayaccordingly be scheduled to receive (e.g., in DL or SL), or to transmit(e.g. in UL or SL) the scheduled transmission. Scheduling transmissionmay in particular be considered to comprise configuring a scheduleddevice with resource/s for this transmission, and/or informing thedevice that the transmission is intended and/or scheduled for someresources. A transmission may be scheduled to cover a time interval, inparticular a successive number of symbols, which may form a continuousinterval in time between (and including) a starting symbol and an endingsymbols. The starting symbol and the ending symbol of a (e.g.,scheduled) transmission may be within the same transmission timingstructure, e.g. the same slot. However, in some cases, the ending symbolmay be in a later transmission timing structure than the startingsymbol, in particular a structure following in time. To a scheduledtransmission, a duration may be associated and/or indicated, e.g. in anumber of symbols or associated time intervals. In some variants, theremay be different transmissions scheduled in the same transmission timingstructure. A scheduled transmission may be considered to be associatedto a specific channel, e.g. a shared channel like PUSCH or PDSCH.

In the context of this disclosure, there may be distinguished betweendynamically scheduled or aperiodic transmission and/or configuration,and semi-static or semi-persistent or periodic transmission and/orconfiguration. The term “dynamic” or similar terms may generally pertainto configuration/transmission valid and/or scheduled and/or configuredfor (relatively) short timescales and/or a (e.g., predefined and/orconfigured and/or limited and/or definite) number of occurrences and/ortransmission timing structures, e.g. one or more transmission timingstructures like slots or slot aggregations, and/or for one or more(e.g., specific number) of transmission/occurrences. Dynamicconfiguration may be based on low-level signaling, e.g. controlsignaling on the physical layer and/or MAC layer, in particular in theform of DCI or SCI. Periodic/semi-static may pertain to longertimescales, e.g. several slots and/or more than one frame, and/or anon-defined number of occurrences, e.g., until a dynamic configurationcontradicts, or until a new periodic configuration arrives. A periodicor semi-static configuration may be based on, and/or be configured with,higher-layer signaling, in particular RCL layer signaling and/or RRCsignaling and/or MAC signaling.

A transmission timing structure may comprise a plurality of symbols,and/or define an interval comprising several symbols (respectively theirassociated time intervals). In the context of this disclosure, it shouldbe noted that a reference to a symbol for ease of reference may beinterpreted to refer to the time domain projection or time interval ortime component or duration or length in time of the symbol, unless it isclear from the context that the frequency domain component also has tobe considered. Examples of transmission timing structures include slot,subframe, mini-slot (which also may be considered a substructure of aslot), slot aggregation (which may comprise a plurality of slots and maybe considered a superstructure of a slot), respectively their timedomain component. A transmission timing structure may generally comprisea plurality of symbols defining the time domain extension (e.g.,interval or length or duration) of the transmission timing structure,and arranged neighboring to each other in a numbered sequence. A timingstructure (which may also be considered or implemented assynchronisation structure) may be defined by a succession of suchtransmission timing structures, which may for example define a timinggrid with symbols representing the smallest grid structures. Atransmission timing structure, and/or a border symbol or a scheduledtransmission may be determined or scheduled in relation to such a timinggrid. A transmission timing structure of reception may be thetransmission timing structure in which the scheduling control signalingis received, e.g. in relation to the timing grid. A transmission timingstructure may in particular be a slot or subframe or in some cases, amini-slot.

Feedback signaling may be considered a form or control signaling, e.g.uplink or sidelink control signaling, like UCI (Uplink ControlInformation) signaling or SCI (Sidelink Control Information) signaling.Feedback signaling may in particular comprise and/or representacknowledgement signaling and/or acknowledgement information and/ormeasurement reporting.

Acknowledgement information may comprise an indication of a specificvalue or state for an acknowledgement signaling process, e.g. ACK orNACK or DTX. Such an indication may for example represent a bit or bitvalue or bit pattern or an information switch. Different levels ofacknowledgement information, e.g. providing differentiated informationabout quality of reception and/or error position in received dataelement/s may be considered and/or represented by control signaling.Acknowledgment information may generally indicate acknowledgment ornon-acknowledgment or non-reception or different levels thereof, e.g.representing ACK or NACK or DTX.

Acknowledgment information may pertain to one acknowledgement signalingprocess. Acknowledgement signaling may comprise acknowledgementinformation pertaining to one or more acknowledgement signalingprocesses, in particular one or more HARQ or ARQ processes. It may beconsidered that to each acknowledgment signaling process theacknowledgement information pertains to, a specific number of bits ofthe information size of the control signaling is assigned. Measurementreporting signaling may comprise measurement information.

Signaling may generally comprise one or more symbols and/or signalsand/or messages. A signal may comprise and/or represent one or morebits, which may be modulated into a common modulated signal. Anindication may represent signaling, and/or be implemented as a signal,or as a plurality of signals. One or more signals may be included inand/or represented by a message. Signaling, in particular controlsignaling, may comprise a plurality of signals and/or messages, whichmay be transmitted on different carriers and/or be associated todifferent acknowledgement signaling processes, e.g. representing and/orpertaining to one or more such processes. An indication may comprisesignaling and/or a plurality of signals and/or messages and/or may becomprised therein, which may be transmitted on different carriers and/orbe associated to different acknowledgement signaling processes, e.g.representing and/or pertaining to one or more such processes.

Signaling utilising, and/or on and/or associated to, resources or aresource structure may be signaling covering the resources or structure,signaling on the associated frequency/ies and/or in the associated timeinterval/s. It may be considered that a signaling resource structurecomprises and/or encompasses one or more substructures, which may beassociated to one or more different channels and/or types of signalingand/or comprise one or more holes (resource element/s not scheduled fortransmissions or reception of transmissions). A resource substructure,e.g. a feedback resource structure, may generally be continuous in timeand/or frequency, within the associated intervals. It may be consideredthat a substructure, in particular a feedback resource structure,represents a rectangle filled with one or more resource elements intime/frequency space. However, in some cases, a resource structure orsubstructure, in particular a frequency resource range, may represent anon-continuous pattern of resources in one or more domains, e.g. timeand/or frequency. The resource elements of a substructure may bescheduled for associated signaling.

It should generally be noted that the number of bits or a bit rateassociated to specific signaling that can be carried on a resourceelement may be based on a modulation and coding scheme (MCS). Thus, bitsor a bit rate may be seen as a form of resources representing a resourcestructure or range in frequency and/or time, e.g. depending on MCS. TheMCS may be configured or configurable, e.g. by control signaling, e.g.DCI or MAC (Medium Access Control) or RRC (Radio Resource Control)signaling.

Different formats of for control information may be considered, e.g.different formats for a control channel like a Physical Uplink ControlChannel (PUCCH). PUCCH may carry control information or correspondingcontrol signaling, e.g. Uplink Control Information (UCI). UCI maycomprise feedback signaling, and/or acknowledgement signaling like HARQfeedback (ACK/NACK), and/or measurement information signaling, e.g.comprising Channel Quality Information (CQI), and/or Scheduling Request(SR) signaling. One of the supported PUCCH formats may be short, and maye.g. occur at the end of a slot interval, and/or multiplexed and/orneighboring to PUSCH. Similar control information may be provided on asidelink, e.g. as Sidelink Control Information (SCI), in particular on a(physical) sidelink control channel, like a (P)SCCH.

A code block may be considered a subelement of a data element like atransport block, e.g., a transport block may comprise a one or aplurality of code blocks, which may be arranged or grouped in code blockgroups.

A scheduling assignment may be configured with control signaling, e.g.downlink control signaling or sidelink control signaling. Such controlssignaling may be considered to represent and/or comprise schedulingsignaling, which may indicate scheduling information. A schedulingassignment may be considered scheduling information indicatingscheduling of signaling/transmission of signaling, in particularpertaining to signaling received or to be received by the deviceconfigured with the scheduling assignment. It may be considered that ascheduling assignment may indicate data (e.g., data block or elementand/or channel and/or data stream) and/or an (associated)acknowledgement signaling process and/or resource/s on which the data(or, in some cases, reference signaling) is to be received and/orindicate resource/s for associated feedback signaling, and/or a feedbackresource range on which associated feedback signaling is to betransmitted. Transmission associated to an acknowledgement signalingprocess, and/or the associated resources or resource structure, may beconfigured and/or scheduled, for example by a scheduling assignment.Different scheduling assignments may be associated to differentacknowledgement signaling processes. A scheduling assignment may beconsidered an example of downlink control information or signaling, e.g.if transmitted by a network node and/or provided on downlink (orsidelink control information if transmitted using a sidelink and/or by auser equipment).

A scheduling grant (e.g., uplink grant) may represent control signaling(e.g., downlink control information/signaling). It may be consideredthat a scheduling grant configures the signaling resource range and/orresources for uplink (or sidelink) signaling, in particular uplinkcontrol signaling and/or feedback signaling, e.g. acknowledgementsignaling. Configuring the signaling resource range and/or resources maycomprise configuring or scheduling it for transmission by the configuredradio node. A scheduling grant may indicate a channel and/or possiblechannels to be used/usable for the feedback signaling, in particularwhether a shared channel like a PUSCH may be used/is to be used. Ascheduling grant may generally indicate uplink resource/s and/or anuplink channel and/or a format for control information pertaining toassociated scheduling assignments. Both grant and assignment/s may beconsidered (downlink or sidelink) control information, and/or beassociated to, and/or transmitted with, different messages.

A resource structure in frequency domain (which may be referred to asfrequency interval and/or range) may be represented by a subcarriergrouping. A subcarrier grouping may comprise one or more subcarriers,each of which may represent a specific frequency interval, and/orbandwidth. The bandwidth of a subcarrier, the length of the interval infrequency domain, may be determined by the subcarrier spacing and/ornumerology. The subcarriers may be arranged such that each subcarrierneighbours at least one other subcarrier of the grouping in frequencyspace (for grouping sizes larger than 1). The subcarriers of a groupingmay be associated to the same carrier, e.g. configurably or configuredof predefined. A physical resource block may be consideredrepresentative of a grouping (in frequency domain). A subcarriergrouping may be considered to be associated to a specific channel and/ortype of signaling, it transmission for such channel or signaling isscheduled and/or transmitted and/or intended and/or configured for atleast one, or a plurality, or all subcarriers in the grouping. Suchassociation may be time-dependent, e.g. configured or configurable orpredefined, and/or dynamic or semi-static. The association may bedifferent for different devices, e.g. configured or configurable orpredefined, and/or dynamic or semi-static. Patterns of subcarriergroupings may be considered, which may comprise one or more subcarriergroupings (which may be associated to same or differentsignalings/channels), and/or one or more groupings without associatedsignaling (e.g., as seen from a specific device). An example of apattern is a comb, for which between pairs of groupings associated tothe same signaling/channel there are arranged one or more groupingsassociated to one or more different channels and/or signaling types,and/or one or more groupings without associated channel/signaling). Itshould be noted that utilised resource structures or resource may appearshifted in time between a transmitter and receiver, during pathtraveling time of signaling between them. Nevertheless, the use ofresources is well-defined from each transmitter's and receiver's pointof view, as it may be assumed that they are aware of such delays.

Example types of signaling comprise signaling of a specificcommunication direction, in particular, uplink signaling, downlinksignaling, sidelink signaling, as well as reference signaling (e.g., SRSor CRS or CSI-RS), communication signaling, control signaling, and/orsignaling associated to a specific channel like PUSCH, PDSCH, PUCCH,PDCCH, PSCCH, PSSCH, etc.).

URLLC may represent a quality requirement on signaling, e.g. regardinglatency and/or reliability (e.g., in terms or BLER or BER), which may behigher or stricter than eMBB, which may aim at lesstime-critical/reliable signaling than URLLC signaling.

In this disclosure, for purposes of explanation and not limitation,specific details are set forth (such as particular network functions,processes and signaling steps) in order to provide a thoroughunderstanding of the technique presented herein. It will be apparent toone skilled in the art that the present concepts and aspects may bepracticed in other variants and variants that depart from these specificdetails.

For example, the concepts and variants are partially described in thecontext of Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or NewRadio mobile or wireless communications technologies; however, this doesnot rule out the use of the present concepts and aspects in connectionwith additional or alternative mobile communication technologies such asthe Global System for Mobile Communications (GSM). While describedvariants may pertain to certain Technical Specifications (TSs) of theThird Generation Partnership Project (3GPP), it will be appreciated thatthe present approaches, concepts and aspects could also be realized inconnection with different Performance Management (PM) specifications.

Moreover, those skilled in the art will appreciate that the services,functions and steps explained herein may be implemented using softwarefunctioning in conjunction with a programmed microprocessor, or using anApplication Specific Integrated Circuit (ASIC), a Digital SignalProcessor (DSP), a Field Programmable Gate Array (FPGA) or generalpurpose computer. It will also be appreciated that while the variantsdescribed herein are elucidated in the context of methods and devices,the concepts and aspects presented herein may also be embodied in aprogram product as well as in a system comprising control circuitry,e.g. a computer processor and a memory coupled to the processor, whereinthe memory is encoded with one or more programs or program products thatexecute the services, functions and steps disclosed herein.

It is believed that the advantages of the aspects and variants presentedherein will be fully understood from the foregoing description, and itwill be apparent that various changes may be made in the form,constructions and arrangement of the exemplary aspects thereof withoutdeparting from the scope of the concepts and aspects described herein orwithout sacrificing all of its advantageous effects. The aspectspresented herein can be varied in many ways.

Some useful abbreviations comprise

Abbreviation Explanation ACK/NACK Acknowledgment/NegativeAcknowledgement ARQ Automatic Repeat reQuest BER Bit Error Rate BLERBlock Error Rates CAZAC Constant Amplitude Zero Cross Correlation CBCode Block CBG Code Block Group CDM Code Division Multiplex CM CubicMetric CQI Channel Quality Information CRC Cyclic Redundancy Check CRSCommon reference signal CSI Channel State Information CSI-RS Channelstate information reference signal DAI Downlink Assignment Indicator DCIDownlink Control Information DFT Discrete Fourier Transform DM(−)RSDemodulation reference signal(ing) eMBB enhanced Mobile BroadBand FDDFrequency Division Duplex FDM Frequency Division Multiplex HARQ HybridAutomatic Repeat Request IFFT Inverse Fast Fourier Transform MAC MediumAccess Control MBB Mobile Broadband MCS Modulation and Coding SchemeMIMO Multiple-input-multiple-output MRC Maximum-ratio combining MRTMaximum-ratio transmission MU-MIMO Multiusermultiple-input-multiple-output OFDM/A Orthogonal Frequency DivisionMultiplex/Multiple Access PAPR Peak to Average Power Ratio PDCCHPhysical Downlink Control Channel PDSCH Physical Downlink Shared ChannelPRACH Physical Random Access CHannel PRB Physical Resource Block PUCCHPhysical Uplink Control Channel PUSCH Physical Uplink Shared Channel(P)SCCH (Physical) Sidelink Control Channel (P)SSCH (Physical) SidelinkShared Channel RAN Radio Access Network RAT Radio Access Technology RBResource Block RNTI Radio Network Temporary Identifier RRC RadioResource Control SA Scheduling Assignment SC-FDM/A Single CarrierFrequency Division Multiplex/Multiple Access SCI Sidelink ControlInformation SINR Signal-to-interference-plus-noise ratio SIRSignal-to-interference ratio SNR Signal-to-noise-ratio SR SchedulingRequest SRS Sounding Reference Signal(ing) SVD Singular-valuedecomposition TB Transport Block TDD Time Division Duplex TDM TimeDivision Multiplex UCI Uplink Control Information UE User EquipmentUL-SCH Uplink Shared Channel, mapped to a PUSCH URLLC Ultra Low LatencyHigh Reliability Communication VL-MIMO Very-largemultiple-input-multiple-output ZF Zero Forcing

Abbreviations may be considered to follow 3GPP usage if applicable.

1. A method of operating a wireless device in a wireless communicationnetwork, the wireless device being triggered for transmitting firstsignaling representing first information on a first resource structure,second signaling representing second information on a second resourcestructure and third signaling representing third information on a thirdresource structure, the second resource structure at least partiallyoverlapping with at least one of the first resource structure and thethird resource structure, the second resource structure being associatedto a lower priority of transmission than the first resource structureand the third resource structure, the method comprising: transmittingthe first information and the third information, omitting transmittingat least one of the second signaling and second information.
 2. Awireless device for a wireless communication network, the wirelessdevice being configured for being triggered for transmitting firstsignaling representing first information on a first resource structure,second signaling representing second information on a second resourcestructure and third signaling representing third information on a thirdresource structure, the second resource structure at least partiallyoverlapping with at least one of the first resource structure and thethird resource structure, the second resource structure being associatedto a lower priority of transmission than the first resource structureand the third resource structure, the wireless device being configuredfor: transmitting the first information and the third information,omitting transmitting at least one of the second signaling and secondinformation.
 3. A method of operating a network node in a wirelesscommunication network, the method comprising: receiving signaling from awireless device, the wireless device being triggered for transmittingfirst signaling representing first information on a first resourcestructure, second signaling representing second information on a secondresource structure and third signaling representing third information ona third resource structure, the second resource structure at leastpartially overlapping with at least one of the first resource structureand the third resource structure, the second resource structure beingassociated to a lower priority of transmission than the first resourcestructure and the third resource structure, receiving signalingcomprises receiving signaling representing the first information and thethird information, omitting the second information.
 4. A network nodefor a wireless communication network, the network node being configuredfor: receiving signaling from a wireless device, the wireless devicebeing triggered for transmitting first signaling representing firstinformation on a first resource structure, second signaling representingsecond information on a second resource structure and third signalingrepresenting third information on a third resource structure, the secondresource structure at least partially overlapping with at least one ofthe first resource structure and the third resource structure, thesecond resource structure being associated to a lower priority oftransmission than the first resource structure and the third resourcestructure, receiving signaling comprises receiving signalingrepresenting the first information and the third information, omittingthe second information.
 5. The method according to claim 1, wherein thefirst resource structure, the second resource structure and the thirdresource structure are in the same transmission timing structure.
 6. Themethod according to claim 1, wherein at least one of: a first priorityof the first signaling is associated to a first transmission quality; asecond priority of the second signaling is associated to secondtransmission quality; and a third priority of the third signaling isassociated to a third transmission quality.
 7. The method according toclaim 1, wherein the first information and third information aremultiplexed and transmitted on a common resource structure.
 8. Themethod according to claim 1, wherein the first signaling is transmittedon the first resource structure and the third signaling is transmittedon the third resource structure.
 9. The method according to claim 1,wherein the first signaling, second signaling and third signalingrepresent control signaling.
 10. The method according to claim 1,wherein transmission of signaling representing the second information ispostponed.
 11. A computer storage medium storing a computer programcomprising instructions configured to cause processing circuitry to atleast one of control and perform a method, the method comprising:receiving signaling from a wireless device, the wireless device beingtriggered for transmitting first signaling representing firstinformation on a first resource structure, second signaling representingsecond information on a second resource structure and third signalingrepresenting third information on a third resource structure, the secondresource structure at least partially overlapping with at least one ofthe first resource structure and the third resource structure, thesecond resource structure being associated to a lower priority oftransmission than the first resource structure and the third resourcestructure, receiving signaling comprises receiving signalingrepresenting the first information and the third information, omittingthe second information.
 12. (canceled)
 13. The method according to claim3, wherein the first resource structure, the second resource structureand the third resource structure are in the same transmission timingstructure.
 14. The method according to claim 3, wherein at least one of:a first priority of the first signaling is associated to a firsttransmission quality; a second priority of the second signaling isassociated to second transmission quality; and a third priority of thethird signaling is associated to a third transmission quality.
 15. Themethod according to claim 3, wherein the first information and thirdinformation are multiplexed and transmitted on a common resourcestructure.
 16. The method according to claim 3, wherein the firstsignaling is transmitted on the first resource structure and the thirdsignaling is transmitted on the third resource structure.
 17. The methodaccording to claim 3, wherein the first signaling, second signaling andthird signaling represent control signaling.
 18. The method according toclaim 3, wherein transmission of signaling representing the secondinformation is postponed.
 19. The method according to claim 5, whereinat least one of: a first priority of the first signaling is associatedto a first transmission quality; a second priority of the secondsignaling is associated to second transmission quality; and a thirdpriority of the third signaling is associated to a third transmissionquality.
 20. The method according to claim 5, wherein the firstinformation and third information are multiplexed and transmitted on acommon resource structure.
 21. The method according to claim 5, whereinthe first signaling is transmitted on the first resource structure andthe third signaling is transmitted on the third resource structure.